Skip to content

[Feature Request] A2A protocol host should support passing Bearer token at runtime for MCP tools #2958

@itsdruvaraj

Description

@itsdruvaraj

Summary

A2A (Agent-to-Agent) protocol hosts should support passing Bearer tokens to MCP tools at runtime when using existing Foundry agents.

Problem

When hosting an existing Azure AI Foundry agent via A2A protocol, there's no way to pass dynamic Bearer tokens to MCP tools during RunAsync() calls. The token must be configured at agent creation time, which doesn't work for A2A hosts that need runtime authentication.

Requested Enhancement

Support passing Bearer token headers through AgentRunOptions or McpServerToolApprovalResponseContent when invoking an existing agent.

Environment

  • .NET 10 SDK
  • Microsoft.Agents.AI 1.0.0-preview
  • Azure.AI.Agents.Persistent (latest preview)

Metadata

Metadata

Labels

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions