New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

a2a_handoff

Hand off over Agent-to-Agent (A2A). With an allow/require_rx decision: the order intent goes to the licensed counterparty's agent (envelope + card URL). With a deny for a patient, the public or an unauthorized actor: returns real licensed destinations from the provider directory (dispensers, pres...

SERVERA2A-Peptides SOURCEhttps://mcp.a2a-peptides.ai/mcp
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/a2a-peptides/a2a-handoff.md

What a2a_handoff does on A2A-Peptides

AI agents call a2a_handoff to retrieve information from A2A-Peptides without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit integer —
intent_id object —
decision_id object —
practice_scope object —
counterparty_card_url object —

Parameters from the server's own tool schema.

Why a2a_handoff is rated Low

Even though a2a_handoff only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about a2a_handoff

What does the a2a_handoff tool do? +

Hand off over Agent-to-Agent (A2A). With an allow/require_rx decision: the order intent goes to the licensed counterparty's agent (envelope + card URL). With a deny for a patient, the public or an unauthorized actor: returns real licensed destinations from the provider directory (dispensers, prescribers) filtered by the decision's jurisdiction, state/province and practice scope — a referral, never a vial. It is categorised as a Read tool in the A2A-Peptides MCP Server, which means it retrieves data without modifying state.

What parameters does a2a_handoff accept? +

a2a_handoff accepts 5 parameters: limit, intent_id, decision_id, practice_scope, counterparty_card_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on a2a_handoff? +

Register the A2A-Peptides MCP server in PolicyLayer and add a rule for a2a_handoff: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches A2A-Peptides. Nothing to install.

What risk level is a2a_handoff? +

a2a_handoff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit a2a_handoff? +

Yes. Add a rate_limit block to the a2a_handoff rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block a2a_handoff completely? +

Set action: deny in the PolicyLayer policy for a2a_handoff. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides a2a_handoff? +

a2a_handoff is provided by the A2A-Peptides MCP server (https://mcp.a2a-peptides.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on A2A-Peptides, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of A2A-Peptides's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.