Execute multiple tasks in parallel using Specialist instances (Manager only)
AI agents invoke executeParallel to trigger actions in tmux-claude 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 triggers execution of arbitrary tasks across multiple Specialist instances. While the effects depend on what tasks are submitted, the core function is to execute operations rather than merely read or write data.
From the tool's definition Tool name explicitly states 'executeParallel' and description says 'Execute multiple tasks in parallel using Specialist instances'. The word 'Execute' combined with the ability to run multiple tasks in parallel indicates code/operation execution.
Documented attack patterns abuse exactly the kind of access executeParallel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and tmux-claude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for executeParallel:
{
"version": "1",
"default": "deny",
"tools": {
"executeParallel": {
"limits": [
{
"counter": "executeparallel_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}executeParallel stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute multiple tasks in parallel using Specialist instances (Manager only). It is categorised as a Execute tool in the tmux-claude MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the tmux-claude MCP Server MCP server in PolicyLayer and add a rule for executeParallel: 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 tmux-claude MCP Server. Nothing to install.
executeParallel 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 executeParallel 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 executeParallel. 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.
executeParallel is provided by the tmux-claude MCP Server MCP server (michael-abdo/tmux-claude-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from tmux-claude MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 tmux-claude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.