Critical Risk →

wikijs_cleanup_orphaned_mappings

Clean up file-to-page mappings for pages that no longer exist in Wiki.js.

How to control wikijs_cleanup_orphaned_mappings ↓

AI agents call wikijs_cleanup_orphaned_mappings 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.

Critical Risk

'Clean up' mappings implies irreversible deletion of mapping records. While the pages themselves no longer exist, removing these mappings cannot be undone. The presence of sibling tools like wikijs_batch_delete_pages and wikijs_delete_page on this server reinforces that destructive operations are common here.

From the tool's definition Clean up file-to-page mappings for pages that no longer exist in Wiki.js

Documented attack patterns abuse exactly the kind of access wikijs_cleanup_orphaned_mappings 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_cleanup_orphaned_mappings:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "wikijs_cleanup_orphaned_mappings"
  ]
}

wikijs_cleanup_orphaned_mappings disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Wiki Js — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the wikijs_cleanup_orphaned_mappings tool do? +

Clean up file-to-page mappings for pages that no longer exist in Wiki.js. 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.

How do I enforce a policy on wikijs_cleanup_orphaned_mappings? +

Register the Wiki Js MCP server in PolicyLayer and add a rule for wikijs_cleanup_orphaned_mappings: 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.

What risk level is wikijs_cleanup_orphaned_mappings? +

wikijs_cleanup_orphaned_mappings is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit wikijs_cleanup_orphaned_mappings? +

Yes. Add a rate_limit block to the wikijs_cleanup_orphaned_mappings 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.

How do I block wikijs_cleanup_orphaned_mappings completely? +

Set action: deny in the PolicyLayer policy for wikijs_cleanup_orphaned_mappings. 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.

What MCP server provides wikijs_cleanup_orphaned_mappings? +

wikijs_cleanup_orphaned_mappings 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.

Enforce policy on every Wiki Js tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.