Clean up stale agents with enhanced options and optional room cleanup
AI agents call cleanup_stale_agents to permanently remove resources in ZMCPTools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes stale agent entries and optionally their associated rooms from the orchestration platform. Removing agents and rooms is an irreversible destructive operation that could disrupt active multi-agent workflows if agents are incorrectly identified as stale. High severity because misuse could terminate legitimate agent coordination across complex development workflows.
From the tool's definition 'Clean up stale agents' and 'optional room cleanup' — removal of agent records and associated rooms is irreversible deletion of coordination state
Documented attack patterns abuse exactly the kind of access cleanup_stale_agents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanup_stale_agents:
{
"version": "1",
"default": "deny",
"hide": [
"cleanup_stale_agents"
]
}cleanup_stale_agents disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clean up stale agents with enhanced options and optional room cleanup. It is categorised as a Destructive tool in the ZMCPTools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for cleanup_stale_agents: 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 ZMCPTools. Nothing to install.
cleanup_stale_agents is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cleanup_stale_agents 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 cleanup_stale_agents. 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.
cleanup_stale_agents is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.