← Back to the briefs
Tools

Microsoft tightens network boundaries and MCP sessions in Agent Framework dotnet-1.28.0

Microsoft has released dotnet-1.28.0 of its Agent Framework, introducing general computer tool execution while breaking declarative workflow network defaults, isolating MCP clients per run, and restricting built-in agent-to-agent responses.

Workflow network rules and ephemeral MCP clients

The dotnet-1.28.0 release restructures how declarative agent workflows interact with external infrastructure. Workflows issuing outgoing HTTP requests must now provide an explicit host and port allowlist through an application-owned handler factory. Empty allowlists block all traffic automatically, and configuration requires exact endpoint matches because subdomains and wildcards are barred.

Tooling using the Model Context Protocol in declarative routines also shifts away from persistent state. The engine now creates and disposes a distinct MCP client for each individual tool call rather than keeping cached sessions open across checkpoint resumes or human approvals. Systems requiring continuous state across operations must now supply durable workflow state or implement a custom handler.

Agent communication and diagnostic constraints

Microsoft altered inter-agent hosting defaults by removing automatic task handling from built-in registrations. Handlers now finish runs with single message responses instead of full task lifecycles, and built-in setups leave cancellation and state resumption unsupported until multi-host mechanisms are reworked. Applications that depend on persistent task tracking must supply their own lifecycle components.

Code execution diagnostics have been tightened as well. Hyperlight and local execution providers now scrub internal host exception details from error messages by default to avoid leaking internal operational data. Additionally, GitHub Copilot agent integrations run with file hooks turned off by default for both new and resumed sessions.

Computer tooling and telemetry adjustments

Alongside isolation measures, the release brings generally available computer-use tools to Foundry hosting, complete with batched call execution. Telemetry layers have retired legacy payload fields to align with GenAI OpenTelemetry patterns, rendering previous sensitive data switches obsolete. Safety checks in memory management now block memory wipe requests lacking proper scope identifiers.

Our assessment

Teams upgrading .NET agent workflows should immediately inspect external HTTP destinations and MCP tool configurations. Because outgoing requests now require precise port designations, existing workflows contacting third-party APIs without exact allowlists will fail at runtime. Operators relying on long-lived MCP session memory must also refactor workflows to preserve context externally, as server-side state no longer survives between tool calls.

Source: Microsoft original publication.

Original source

Read the original material

Microsoft (opens in a new tab)

The article date belongs to Agentic Horizon. The source publication date is listed separately. Vendor claims remain attributed; we have not independently tested the reported capability.

Search the publication

Find a story by title, topic, or keyword.

Press Escape to close

Ask HorizonYour site guide
Your guide to the publication

Ask Horizon.

Ask a question about the publication.

Privacy