Distribute tasks across multiple Managers (Executive only)
AI agents invoke distributeWork 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 orchestration of work across multiple Claude instances/managers via tmux. It initiates external operations whose effects depend on the arguments (what tasks are distributed), making it Execute. The 'Executive only' restriction and multi-instance orchestration imply a high blast radius if misused—incorrect distribution could spawn unintended agents or workflows across the system.
From the tool's definition Distribute tasks across multiple Managers (Executive only)
Documented attack patterns abuse exactly the kind of access distributeWork 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 distributeWork:
{
"version": "1",
"default": "deny",
"tools": {
"distributeWork": {
"limits": [
{
"counter": "distributework_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}distributeWork 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.
Distribute tasks across multiple Managers (Executive 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 distributeWork: 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.
distributeWork 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 distributeWork 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 distributeWork. 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.
distributeWork 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.