Blog

Microsoft & Copilot agents

semantic-kernelmicrosoftsdkacquisition

Semantic Kernel tool calling with verification (2026)

Wrap SK plugins and planners with verifyAction so policy stays consistent across .NET and Python agents. 6-min guide with checklist, FAQ answers, and SDK…

May 30, 20266 min read

Wrap SK plugins and planners with verifyAction so policy stays consistent across .NET and Python agents. If you found this via microsoft, you likely need software this week — not another strategy deck. Sanctum Runtime combines an MIT SDK with a hosted console for execution-time approve, verify, and block.

Semantic Kernel tool calling with verification: what teams should know

Open console.sanctumruntime.com, connect one agent with @sanctum-runtime/sdk, and gate one real action today. No sales call required for the first approval workflow.

Does Sanctum replace my model provider or gateway?

No. Sanctum sits at the action boundary — approve, verify, or block tool side effects — alongside OpenAI, Anthropic, Google, Microsoft, or gateway vendors.

Key takeaways

  • Discovery channel: microsoft — intent is deploy or compare, not casual reading.
  • Runtime trust gates side effects before they run; guardrails alone miss tool calls.
  • Successful pilots typically gate email, payments, or production writes in week one.

Implementation checklist

  1. Console → Agents → register agent → copy SDK snippet.
  2. Shield Rules → Verify on highest-risk action for your stack.
  3. Run one held action → approve on Overview or mobile PWA.
  4. Compliance → export audit sample for security or investor review.

People also ask

Where should I start if this article matches my search?

Open console.sanctumruntime.com, connect one agent with @sanctum-runtime/sdk, and gate one real action today. No sales call required for the first approval workflow.

Does Sanctum replace my model provider or gateway?

No. Sanctum sits at the action boundary — approve, verify, or block tool side effects — alongside OpenAI, Anthropic, Google, Microsoft, or gateway vendors.

How does this help us reach production safely?

You get policy versioning, human review queues, fleet pause, and audit exports — the artifacts security, finance, and insurance reviewers ask for when agents act autonomously.

Guides: agentic AI risk · MCP security · runtime authorization · HITL approvals · coding agents · get startedMore: all posts · AI trust layer · open Sanctum Console

Give every agent action a trust boundary.

Start with Connect Agent, keep the SDK path for deeper fleets, and prove exactly what was approved, blocked, or contained.