Find documents in a MongoDB collection using a JSON filter and projection.
AI agents call find-documents to retrieve information from Universal Mcp Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a MongoDB collection based on filter criteria and projection parameters. It has no side effects—it does not create, modify, delete, or execute operations. It is a standard read operation that queries existing data. Severity is low because even if misused, it only exposes data retrieval with no destructive or operational consequences.
From the tool's definition Tool description states 'Find documents in a MongoDB collection using a JSON filter and projection.' The verb 'find' with 'filter and projection' indicates querying/retrieving data without modification.
Attacks that exploit this kind of access
Find documents in a MongoDB collection using a JSON filter and projection. It is categorised as a Read tool in the Universal Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Universal Mcp Toolkit MCP server in PolicyLayer and add a rule for find-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 Universal Mcp Toolkit. Nothing to install.
find-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 find-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 find-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.
find-documents is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →