AI agents call delete_pages_by_ids 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 permanently removes pages from the system based on provided IDs. Deletion is inherently irreversible and cannot be undone, making it destructive rather than merely Write. Given the multi-agent orchestration context where an AI could be manipulated into deleting critical pages, the high severity reflects significant blast radius despite the operation being straightforward.
From the tool's definition Tool name contains 'delete' and description states 'Delete specific pages by their IDs'. The verb 'delete' explicitly indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_pages_by_ids 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 delete_pages_by_ids:
{
"version": "1",
"default": "deny",
"hide": [
"delete_pages_by_ids"
]
}delete_pages_by_ids 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.
Delete specific pages by their IDs. 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 delete_pages_by_ids: 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.
delete_pages_by_ids 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 delete_pages_by_ids 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 delete_pages_by_ids. 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.
delete_pages_by_ids 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.