get_document_annotations
AI agents call get_document_annotations to retrieve information from IBM Content Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing document annotations without modifying, creating, or destroying data. While the description is empty, the naming convention and position among sibling tools (which include destructive actions like delete_document_version and delete_folder) strongly suggests this is a query operation.
From the tool's definition Tool name 'get_document_annotations' indicates retrieval of annotations attached to documents. The 'get_' prefix and absence of modification language (create, update, delete, apply) suggest a read operation.
Attacks that exploit this kind of access
get_document_annotations. It is categorised as a Read tool in the IBM Content Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for get_document_annotations: 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.
get_document_annotations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_document_annotations 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 get_document_annotations. 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.
get_document_annotations 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 →