Send an encrypted message to another agent.
AI agents use aip_send_message to create or update resources in Aip Identity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aip Identity environment.
Sending messages creates new data (message records, routing information, or communication logs) within the identity system. While encrypted and directed to specific agents, it modifies system state reversibly. This is Write rather than Execute because it does not run code or trigger external operations—it simply transmits data.
From the tool's definition The tool is called 'aip_send_message' and described as 'Send an encrypted message to another agent.' This creates/modifies data (the message record in the messaging system) in a reversible manner.
Attacks that exploit this kind of access
Send an encrypted message to another agent. It is categorised as a Write tool in the Aip Identity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aip Identity MCP server in PolicyLayer and add a rule for aip_send_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 Aip Identity. Nothing to install.
aip_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the aip_send_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 aip_send_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.
aip_send_message is provided by the Aip Identity MCP server (the-nexus-guard/aip-mcp-server). 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 →