Permanently delete a trashed page. THIS IS IRREVERSIBLE — the page content cannot be recovered after this call. The page must already be in the trash (use delete_page first).
AI agents call purge_page to permanently remove resources in Collectives — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data without possibility of recovery. The description explicitly states it is 'IRREVERSIBLE' and that 'page content cannot be recovered'. This unambiguously classifies as Destructive rather than Write (which is reversible) or Execute (which may have recoverable effects).
From the tool's definition Permanently delete a trashed page. THIS IS IRREVERSIBLE — the page content cannot be recovered after this call.
Attacks that exploit this kind of access
Permanently delete a trashed page. THIS IS IRREVERSIBLE — the page content cannot be recovered after this call. The page must already be in the trash (use delete_page first). It is categorised as a Destructive tool in the Collectives MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Collectives MCP server in PolicyLayer and add a rule for purge_page: 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 Collectives. Nothing to install.
purge_page 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 purge_page 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 purge_page. 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.
purge_page is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →