Permanently delete ALL data for an owner. Generates a deletion certificate first. Executor-only, REST phase only. IRREVERSIBLE.
AI agents call purge_owner_data to permanently remove resources in WAKE Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call purge_owner_data doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from WAKE Protocol is gone — there is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Permanently delete ALL data for an owner. Generates a deletion certificate first. Executor-only, REST phase only. IRREVERSIBLE. It is categorised as a Destructive tool in the WAKE Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WAKE Protocol MCP server in PolicyLayer and add a rule for purge_owner_data: 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 WAKE Protocol. Nothing to install.
purge_owner_data 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_owner_data 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_owner_data. 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_owner_data is provided by the WAKE Protocol MCP server (wake-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.