List all collections in the MongoDB database
AI agents call listCollections 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.
This tool performs a simple enumeration of collections, which is a non-destructive query operation. It has minimal blast radius—an agent cannot cause data loss, financial harm, or execute arbitrary operations with this tool alone. The severity is low because knowing what collections exist is metadata disclosure but does not enable modification or deletion of data.
From the tool's definition Tool name 'listCollections' and description 'List all collections in the MongoDB database' indicate a read-only operation that retrieves schema/metadata without modifying data.
Documented attack patterns abuse exactly the kind of access listCollections 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 listCollections:
{
"version": "1",
"default": "deny",
"tools": {
"listCollections": {}
}
}listCollections 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.
List all collections in the MongoDB database. 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 listCollections: 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.
listCollections 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 listCollections 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 listCollections. 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.
listCollections 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.