Send a message from one agent to another via the A2A protocol.
AI agents invoke send_agent_message to trigger actions in Tenzro Ledger MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — dispatching a message between agents via a protocol. It is not a simple data read or write; it causes an action in an external system (agent-to-agent communication), which could trigger downstream agent behaviors. The blast radius is medium since a misused message could cause unintended agent actions, but it doesn't directly move money or destroy data.
From the tool's definition Send a message from one agent to another via the A2A protocol
Attacks that exploit this kind of access
Send a message from one agent to another via the A2A protocol. It is categorised as a Execute tool in the Tenzro Ledger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for send_agent_message: 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 Tenzro Ledger MCP. Nothing to install.
send_agent_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_agent_message 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.
Set action: deny in the PolicyLayer policy for send_agent_message. 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.
send_agent_message is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →