search_documents
AI agents call search_documents to retrieve information from MCP Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs document searching within a read-only document server. Even with an empty description, the context of a secure read-only server with path traversal protection and the presence of sibling read tools (list_documents, read_document) strongly suggests this is a retrieval operation.
From the tool's definition Tool name 'search_documents' combined with server description stating 'list, search, and read local documents' and 'read-only access' indicates this is a search/query operation.
Attacks that exploit this kind of access
search_documents. It is categorised as a Read tool in the MCP Document Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Server MCP server in PolicyLayer and add a rule for search_documents: 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 MCP Document Server. Nothing to install.
search_documents 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 search_documents 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 search_documents. 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.
search_documents is provided by the MCP Document Server MCP server (watsona4/mcp-document-server). 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 →