create_hold
AI agents use create_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.
Creating a legal hold modifies the state of documents/objects by placing them under preservation obligations. This is a Write operation (creates/modifies data reversibly) rather than Read (no side effects), Execute (no code/command execution), Destructive (holds can be deleted), or Financial (no money movement).
From the tool's definition Tool name 'create_hold' indicates creation of a legal hold, a reversible administrative action. Sibling tools include 'delete_hold' and 'add_object_to_hold', confirming holds are created and modified rather than irreversibly destroyed.
Attacks that exploit this kind of access
create_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.
Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_hold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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 →