update_document_properties
AI agents use update_document_properties 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.
This tool creates or modifies document properties reversibly within IBM FileNet Content Manager. While the description is empty (reducing confidence slightly), the name clearly indicates a property update operation on existing documents, which is a Write category action.
From the tool's definition Tool name 'update_document_properties' and context of document lifecycle management system indicate modification of existing document metadata/properties.
Attacks that exploit this kind of access
update_document_properties. 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 update_document_properties: 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.
update_document_properties 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 update_document_properties 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 update_document_properties. 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.
update_document_properties 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 →