Execute a coding task using Claude Code CLI
AI agents invoke claude_code_task to trigger actions in MCP-Claude Code Bridge. 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 arbitrary coding tasks via Claude Code CLI. While the name doesn't explicitly say "run" or "exec", the verb "Execute" in the description combined with the context of building projects, APIs, and scripts means it triggers external operations whose effects depend entirely on the task arguments.
From the tool's definition Tool description states "Execute a coding task using Claude Code CLI"; sibling tools include run_command which suggests arbitrary command execution; server description mentions "creating React apps, building APIs, and debugging scripts" which are all…
Attacks that exploit this kind of access
Execute a coding task using Claude Code CLI. It is categorised as a Execute tool in the MCP-Claude Code Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP-Claude Code Bridge MCP server in PolicyLayer and add a rule for claude_code_task: 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 MCP-Claude Code Bridge. Nothing to install.
claude_code_task 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_code_task 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_code_task. 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_code_task is provided by the MCP-Claude Code Bridge MCP server (sobieskicodes/claude-desktop-mcp-to-claude-agent). 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 →