执行Claude Code任务(同步方式)
AI agents invoke execute_cc_task to trigger actions in Claude Code Multi-Process 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.
This tool runs code (Claude Code tasks) whose effects depend entirely on the code being executed. While the tool itself is not destructive by design, it grants an AI agent the ability to execute arbitrary code, which could perform reads, writes, deletes, or external operations depending on what code is passed to it. This makes it Execute-category.
From the tool's definition Tool named 'execute_cc_task' with description indicating execution of Claude Code tasks in synchronous mode.
Attacks that exploit this kind of access
执行Claude Code任务(同步方式). It is categorised as a Execute tool in the Claude Code Multi-Process MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Code Multi-Process MCP Server MCP server in PolicyLayer and add a rule for execute_cc_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 Claude Code Multi-Process MCP Server. Nothing to install.
execute_cc_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 execute_cc_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 execute_cc_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.
execute_cc_task is provided by the Claude Code Multi-Process MCP Server MCP server (l-x-c/cc-multi-process-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 →