document_search
AI agents call document_search 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.
Search operations are read-only actions that retrieve or query data without side effects. However, severity is elevated to 'medium' because document search in enterprise content systems can expose sensitive metadata, legal documents, or confidential business records depending on access controls and search scope.
From the tool's definition Tool name 'document_search' with no description provided, but situated on a document content management server (IBM FileNet Content Manager) alongside document lifecycle operations. The 'search' naming pattern aligns with query/retrieval operations.
Attacks that exploit this kind of access
document_search. 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 document_search: 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.
document_search 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 document_search 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 document_search. 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.
document_search 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 →