Send a message to an active session
AI agents invoke send_message to trigger actions in Shannon 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.
Sending a message to an active Claude Code CLI session drives the agent to perform actions (run code, execute shell commands, file operations, etc.) whose effects depend entirely on the message content. This is an indirect execution primitive — the blast radius is high because an attacker or misbehaving agent could craft messages that cause the session to perform destructive or sensitive operations.
From the tool's definition "Send a message to an active session" — dispatches input to a running Claude Code CLI session, triggering execution of whatever operation or command the message encodes.
Attacks that exploit this kind of access
Send a message to an active session. It is categorised as a Execute tool in the Shannon MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shannon 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 Shannon MCP. 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 Shannon MCP server (krzemienski/shannon-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 →