Execute a MongoDB query with optional execution plan analysis
AI agents call query to retrieve information from MongoDB without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the word 'Execute' appears in the description, the context makes clear this is executing a query for retrieval purposes only, not executing arbitrary code or commands. The server is explicitly described as providing 'read-only queries,' and the tool includes 'optional execution plan analysis' which is a read-side diagnostic feature.
From the tool's definition Tool description states 'Execute a MongoDB query' and server description explicitly says 'execute read-only queries.' The sibling tools include destructive operations (insert, update, createIndex) which are separate, confirming this tool is limited to read…
Documented attack patterns abuse exactly the kind of access query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MongoDB, and nothing reaches the server without passing your rules. This is the rule we recommend for query:
{
"version": "1",
"default": "deny",
"tools": {
"query": {}
}
}query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a MongoDB query with optional execution plan analysis. It is categorised as a Read tool in the MongoDB MCP Server, which means it retrieves data without modifying state.
Register the MongoDB MCP server in PolicyLayer and add a rule for query: 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 MongoDB. Nothing to install.
query 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 query 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 query. 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.
query is provided by the MongoDB MCP server (kiliczsh/mcp-mongo-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MongoDB, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 MongoDB tools catalogued and risk-classified — across an index of 43,000+ MCP servers.