Run comprehensive cleanup for both agents and rooms with detailed reporting
AI agents call run_comprehensive_cleanup 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.
The tool performs broad cleanup across multiple resource types (agents and rooms). Given the sibling tools that perform irreversible deletions of stale/orphaned resources, this 'comprehensive' version likely does the same at scale. Cleanup operations in orchestration platforms typically remove data permanently.
From the tool's definition 'comprehensive cleanup for both agents and rooms' — cleanup operations typically purge/delete stale or orphaned data irreversibly, consistent with sibling tools 'cleanup_orphaned_projects', 'cleanup_stale_agents', and 'cleanup_stale_analyses'
Documented attack patterns abuse exactly the kind of access run_comprehensive_cleanup 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 run_comprehensive_cleanup:
{
"version": "1",
"default": "deny",
"hide": [
"run_comprehensive_cleanup"
]
}run_comprehensive_cleanup 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.
Run comprehensive cleanup for both agents and rooms with detailed reporting. 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 run_comprehensive_cleanup: 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.
run_comprehensive_cleanup 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 run_comprehensive_cleanup 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 run_comprehensive_cleanup. 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.
run_comprehensive_cleanup 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.