add_object_to_hold · IBM Content Services MCP Server MCP

WHAT IT DOES

What add_object_to_hold does on IBM Content Services MCP Server

AI agents use add_object_to_hold to create or update resources in IBM Content Services MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IBM Content Services MCP Server environment.

WHY IT NEEDS A POLICY

Why add_object_to_hold needs a policy

Legal holds are critical compliance controls that preserve documents for litigation or regulatory purposes. Adding an object to a hold modifies the legal hold state of a document, which is a reversible Write operation. However, the severity is high because misuse could compromise legal compliance, evidence preservation, or create unauthorized holds on sensitive documents.

From the tool's definition Tool name 'add_object_to_hold' indicates adding/modifying legal hold status on documents. Sibling tools include 'create_hold' and 'delete_hold', confirming this operates on holds. The parent server manages 'legal holds' per its description.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_object_to_hold Rate-limited

add_object_to_hold stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_object_to_hold": {
      "limits": [
        {
          "counter": "add_object_to_hold_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches IBM Content Services MCP Server, so you can run agents against it safely.

FAQ

Questions about add_object_to_hold

What does the add_object_to_hold tool do? +

add_object_to_hold. It is categorised as a Write tool in the IBM Content Services MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_object_to_hold? +

Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for add_object_to_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 add_object_to_hold? +

add_object_to_hold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_object_to_hold? +

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

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

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