List all collections in the MongoDB database.
AI agents call list_collections to retrieve information from MongoDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves metadata (collection names) from MongoDB. While it does not modify any data, the severity is elevated to 'medium' because exposing the complete list of collections in a database could enable reconnaissance attacks, allowing an attacker to discover what data exists in the system and potentially target other tools (like read_documents or delete_documents) more…
From the tool's definition Tool name 'list_collections' and description 'List all collections in the MongoDB database' indicate a retrieval operation that queries database metadata without modifying data.
Attacks that exploit this kind of access
List all collections in the MongoDB database. It is categorised as a Read tool in the MongoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MongoDB MCP Server MCP server in PolicyLayer and add a rule for list_collections: 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 MCP Server. Nothing to install.
list_collections 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 list_collections 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 list_collections. 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.
list_collections is provided by the MongoDB MCP Server MCP server (ruslankf777/mcp_mongo). 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 →