delete_page
AI agents call delete_page to permanently remove resources in Logseq MCP Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Page deletion in a knowledge management system is irreversible and cannot be undone through the API. This destroys user data without recovery options. The empty description reduces confidence slightly, but the name unambiguously indicates a destructive operation. Destructive is more severe than Write (which covers reversible create/update operations) because it permanently eliminates data.
From the tool's definition Tool name is 'delete_page' with empty description. Given sibling tools like 'create_page', 'create_block', 'remove_block', and the server's focus on managing a Logseq knowledge graph, 'delete_page' almost certainly irreversibly removes pages and associated…
Attacks that exploit this kind of access
delete_page. It is categorised as a Destructive tool in the Logseq MCP Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Logseq MCP Tools MCP server in PolicyLayer and add a rule for delete_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 Logseq MCP Tools. Nothing to install.
delete_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 delete_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 delete_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.
delete_page is provided by the Logseq MCP Tools MCP server (mikeysrecipes/logseq-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 →