Send a message to another Claude instance
AI agents use send to create or update resources in Claude IPC MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude IPC MCP environment.
Sending a message is a Write operation: it creates a new message and delivers it to another instance. It is reversible in the sense that messages can be ignored, but the act of sending cannot be undone. There is no indication of code execution, deletion, or financial action. Severity is medium because messages sent to other AI instances could trigger further downstream actions depending on the recipient's behavior.
From the tool's definition "Send a message to another Claude instance" — creates and transmits a message to another process
Attacks that exploit this kind of access
Send a message to another Claude instance. It is categorised as a Write tool in the Claude IPC MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude IPC MCP server in PolicyLayer and add a rule for send: 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 Claude IPC MCP. Nothing to install.
send 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 send 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. 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 is provided by the Claude IPC MCP server (jdez427/claude-ipc-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 →