FreshCtx™

Delegation chain ending at a guarded MCP tool

FreshCtx + A2A to MCP delegation

A documented three-agent example where an A2A delegation chain ends at an MCP tool protected by MCP Guard.

What FreshCtx protects

Each hop revalidates its own declared evidence, and the final protected MCP tool is revalidated at the native tools/call boundary before its handler runs.

Where the pre-action boundary sits

Two separate boundaries compose: the A2A receiving-side delegation guard and the MCP tools/call guard. Neither hop inherits the other's freshness result.

Limitations

  • This extra exists for the documented three-agent example that ends at a guarded MCP tool.
  • Authentication, authorization, transactions, retries, and idempotency remain application responsibilities at every hop.
  • Raw MCP arguments and business payloads stay outside FreshCtx metadata and audit records.

Installation

install
python -m pip install 'freshctx[a2a-mcp]==0.16.0'

Minimal example

A2A to MCP delegation · minimal example
python -m pip install 'freshctx[a2a-mcp]==0.16.0'
python examples/a2a_to_mcp_delegation.py

Continue

FreshCtx quickstartFreshCtx homepageExamples ↗AgnoLangGraphOpenAI Agents SDKGoogle Agent Development KitElevenLabsA2A delegation guardMCP Guard

Third-party names and logos are trademarks of their respective owners. Their appearance identifies compatible integration surfaces and does not imply endorsement or partnership.