delete_object_from_hold

delete_object_from_hold

Server IBM Content Services MCP Server mohamedarif-m/filenet-mcp-localfile
Category Destructive
Risk class Critical
Parameters 00 required

What delete_object_from_hold does on IBM Content Services MCP Server

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

Why delete_object_from_hold needs a policy

Removing an object from a legal hold is a destructive and potentially irreversible action in the context of legal/compliance workflows. Legal holds are used to preserve documents for litigation or compliance purposes; removing an object from a hold could expose the organization to legal liability and the action may not be easily reversible if the document is subsequently modified or deleted.

From the tool's definition Tool name 'delete_object_from_hold' combined with sibling tools including 'delete_document_version', 'delete_folder', 'delete_hold' and the 'add_object_to_hold' counterpart suggest irreversible removal of an object from a legal hold.

Questions about delete_object_from_hold

What does the delete_object_from_hold tool do? +

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

How do I enforce a policy on delete_object_from_hold? +

Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for delete_object_from_hold: 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.

What risk level is delete_object_from_hold? +

delete_object_from_hold 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 delete_object_from_hold? +

Yes. Add a rate_limit block to the delete_object_from_hold 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 delete_object_from_hold completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.