Delete a single page.data.<key> (DELETE /pages/{id}/data/{key}).
AI agents call page_delete_data to permanently remove resources in Voog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes page data attributes without undo capability. While scoped to a single key rather than entire pages, it performs irreversible deletion. The DELETE HTTP method and explicit 'Delete' language confirm destructive intent. Severity is high (not critical) because blast radius is limited to individual page data fields rather than entire content structures or databases.
From the tool's definition Tool name contains 'delete' and description states 'Delete a single page.data.<key>' with DELETE HTTP method, indicating irreversible data removal.
Attacks that exploit this kind of access
Delete a single page.data.<key> (DELETE /pages/{id}/data/{key}). It is categorised as a Destructive tool in the Voog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Voog MCP server in PolicyLayer and add a rule for page_delete_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 Voog. Nothing to install.
page_delete_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 page_delete_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 page_delete_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.
page_delete_data is provided by the Voog MCP server (runnel/voog-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 →