Send a prompt to a running OpenClaude session.
AI agents invoke send_prompt to trigger actions in OpenClaude MCP Server. 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 prompt to a running LLM session triggers an external computation/operation whose effects depend on the prompt content. This is an Execute-class action: it causes a live session to process arbitrary input, potentially producing outputs that drive downstream actions (especially given this server's described capabilities like hybrid cloud planning and fleet monitoring).
From the tool's definition "Send a prompt to a running OpenClaude session" — triggers execution of an LLM inference session with user-supplied input
Attacks that exploit this kind of access
Send a prompt to a running OpenClaude session. It is categorised as a Execute tool in the OpenClaude MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenClaude MCP Server MCP server in PolicyLayer and add a rule for send_prompt: 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 OpenClaude MCP Server. Nothing to install.
send_prompt 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_prompt 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_prompt. 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_prompt is provided by the OpenClaude MCP Server MCP server (sandraschi/openclaude-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 →