Purge page version history older than a duration (e.g.
AI agents call wiki_pages_purge_history to permanently remove resources in Mcp Wikijs Mv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes page version history, which cannot be undone. Once historical versions are purged, they cannot be recovered. This is a destructive operation affecting data integrity and audit trails. While not as critical as deleting current pages, irreversible deletion of any data classifies it as Destructive rather than Write.
From the tool's definition Tool name 'wiki_pages_purge_history' and description 'Purge page version history older than a duration' indicate permanent deletion of historical data. The verb 'purge' combined with 'history' explicitly describes irreversible removal of versioned content.
Attacks that exploit this kind of access
Purge page version history older than a duration (e.g. It is categorised as a Destructive tool in the Mcp Wikijs Mv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_pages_purge_history: 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 Mcp Wikijs Mv. Nothing to install.
wiki_pages_purge_history 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 wiki_pages_purge_history 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 wiki_pages_purge_history. 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.
wiki_pages_purge_history is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). 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 →