Run a one-shot prompt against the Claude Code CLI in headless, stateless
AI agents invoke claude_prompt_with_context to trigger actions in Claudecode. 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.
This tool executes prompts against Claude's code execution CLI. Prompts can contain arbitrary instructions to generate, run, or execute code. While the exact capabilities depend on what Claude Code CLI permits, the foundational behavior is triggering code execution whose effects depend on the prompt content supplied by the user.
From the tool's definition Tool description states 'Run a one-shot prompt against the Claude Code CLI in headless, stateless' mode. The server wraps 'Claude's coding capabilities' and enables 'execute Claude Code commands'.
Attacks that exploit this kind of access
Run a one-shot prompt against the Claude Code CLI in headless, stateless. It is categorised as a Execute tool in the Claudecode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claudecode MCP server in PolicyLayer and add a rule for claude_prompt_with_context: 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 Claudecode. Nothing to install.
claude_prompt_with_context 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 claude_prompt_with_context 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 claude_prompt_with_context. 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.
claude_prompt_with_context is provided by the Claudecode MCP server (trevoraspencer/claudecode-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 →