Send a message to a Claude-Code session.
AI agents invoke send_message to trigger actions in Claude Code MCP Controller. 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.
Sending a message to a Claude Code session causes that session to interpret and act on the message, which may result in code execution, file system changes, shell commands, or other operations depending on the message content. The blast radius is high because the downstream effects are unbounded and depend on what the session does in response.
From the tool's definition Send a message to a Claude-Code session — triggers arbitrary natural language commands in an active Claude Code session, which can execute code, run shell commands, modify files, etc.
Attacks that exploit this kind of access
Send a message to a Claude-Code session. It is categorised as a Execute tool in the Claude Code MCP Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Code MCP Controller MCP server in PolicyLayer and add a rule for 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 Claude Code MCP Controller. Nothing to install.
send_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_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_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_message is provided by the Claude Code MCP Controller MCP server (mostafa-drz/claude-code-mcp-controller). 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 →