AI agents call wikijs_delete_hierarchy to permanently remove resources in Wiki Js — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name explicitly uses 'delete', which is a destructive action that cannot be undone. A hierarchy deletion would remove multiple related pages or organizational structures irreversibly. This falls under the Destructive category (not Execute, which would be for reversible operations with conditional effects).
From the tool's definition Tool name 'wikijs_delete_hierarchy' contains the verb 'delete', indicating irreversible removal of data. The sibling tools include 'wikijs_batch_delete_pages', 'wikijs_delete_page', and 'wikijs_cleanup_orphaned_mappings', confirming this server handles page…
Documented attack patterns abuse exactly the kind of access wikijs_delete_hierarchy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wiki Js, and nothing reaches the server without passing your rules. This is the rule we recommend for wikijs_delete_hierarchy:
{
"version": "1",
"default": "deny",
"hide": [
"wikijs_delete_hierarchy"
]
}wikijs_delete_hierarchy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
wikijs_delete_hierarchy. It is categorised as a Destructive tool in the Wiki Js MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wiki Js MCP server in PolicyLayer and add a rule for wikijs_delete_hierarchy: 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 Wiki Js. Nothing to install.
wikijs_delete_hierarchy 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 wikijs_delete_hierarchy 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 wikijs_delete_hierarchy. 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.
wikijs_delete_hierarchy is provided by the Wiki Js MCP server (talosdeus/wiki-js-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Wiki Js tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Wiki Js tools catalogued and risk-classified — across an index of 42,500+ MCP servers.