delete_wiki_page
AI agents call delete_wiki_page to permanently remove resources in WikiJS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of wiki pages is a destructive operation that irreversibly removes data. While the description is uninformative, the tool name and the server's stated capability for 'full management of WikiJS instances' make the destructive nature clear. This warrants high severity due to data loss potential and the blast radius of accidental or malicious deletion of wiki content.
From the tool's definition Tool name 'delete_wiki_page' combined with server context showing full WikiJS instance management. Despite empty description, the name unambiguously indicates irreversible deletion of wiki page content that cannot be undone.
Attacks that exploit this kind of access
delete_wiki_page. It is categorised as a Destructive tool in the WikiJS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for delete_wiki_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 WikiJS MCP Server. Nothing to install.
delete_wiki_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_wiki_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_wiki_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_wiki_page is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-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 →