Get parallel execution status for a Manager
AI agents call getParallelStatus to retrieve information from tmux-claude MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves status information about parallel execution. The use of 'Get' combined with 'status' indicates a read-only operation that observes state without altering it. There is no evidence of code execution, data modification, deletion, or financial operations. The low severity reflects that retrieving status information poses minimal risk if misused by an agent.
From the tool's definition Tool name contains 'Get' and description states 'Get parallel execution status' — a retrieval operation with no indication of side effects, modification, or execution.
Documented attack patterns abuse exactly the kind of access getParallelStatus 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 getParallelStatus:
{
"version": "1",
"default": "deny",
"tools": {
"getParallelStatus": {}
}
} getParallelStatus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get parallel execution status for a Manager. It is categorised as a Read tool in the tmux-claude MCP Server MCP Server, which means it retrieves data without modifying state.
Register the tmux-claude MCP Server MCP server in PolicyLayer and add a rule for getParallelStatus: 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.
getParallelStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getParallelStatus 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 getParallelStatus. 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.
getParallelStatus 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.