search_documents
AI agents call search_documents to retrieve information from Mnemosyne MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_documents' explicitly denotes a retrieval operation. Although the description is empty (lowering confidence slightly), the name and context of the Mnemosyne system—which supports querying and managing knowledge graphs—indicate this performs document search/lookup. This is a Read operation: it retrieves data without creating, modifying, deleting, or executing arbitrary code.
From the tool's definition Tool name 'search_documents' indicates querying/retrieval of documents with no modification capability. Server description confirms it enables 'query' operations on knowledge graphs. Name strongly suggests data retrieval without side effects.
Attacks that exploit this kind of access
search_documents. It is categorised as a Read tool in the Mnemosyne MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemosyne 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 Mnemosyne MCP. 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 Mnemosyne MCP server (sophia-labs/mnemosyne-mcp). 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 →