delete_page
A destructive tool on the Enterprise-Multi-Agent-Engine MCP server.
This record as markdown: /tools/enterprise-multi-agent-engine/delete-page.md
What delete_page does on Enterprise-Multi-Agent-Engine
AI agents call delete_page to permanently remove resources in Enterprise-Multi-Agent-Engine, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_page is rated Critical
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
The rule that runs delete_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enterprise-Multi-Agent-Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_page, this is the rule to start with:
delete_page is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Enterprise-Multi-Agent-Engine, apply this rule, and every delete_page call is checked against it from then on.
Questions about delete_page
delete_page is a destructive tool on the Enterprise-Multi-Agent-Engine MCP server. It is categorised as a Destructive tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enterprise-Multi-Agent-Engine 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 Enterprise-Multi-Agent-Engine. 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 Enterprise-Multi-Agent-Engine MCP server (Mojtaba-Dehghani/Enterprise-Multi-Agent-Engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.
Across the catalogue