delete_document_version
AI agents call delete_document_version to permanently remove resources in IBM Content Services MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of document versions is an irreversible action that permanently removes data from the content management system. This cannot be undone and represents a destructive operation.
From the tool's definition Tool name 'delete_document_version' explicitly indicates deletion of document versions. Sibling tools on the same server include 'delete_folder' and 'delete_hold', confirming this server provides destructive operations.
Attacks that exploit this kind of access
delete_document_version. It is categorised as a Destructive tool in the IBM Content Services MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for delete_document_version: 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 IBM Content Services MCP Server. Nothing to install.
delete_document_version 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_document_version 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_document_version. 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_document_version is provided by the IBM Content Services MCP Server MCP server (mohamedarif-m/filenet-mcp-localfile). 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 →