Count documents in a MongoDB collection
AI agents call mongodb_count to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Counting documents is a read-only operation that queries collection metadata and returns a result without side effects. It does not create, modify, delete, execute code, or move money. The sibling tools show a clear pattern: write operations like mongodb_insert_one, mongodb_insert_many, mongodb_delete_one, mongodb_delete_many, and schema operations like mongodb_create_index and mongodb_drop_index are separate tools.
From the tool's definition Tool is named 'mongodb_count' and described as 'Count documents in a MongoDB collection' — a query operation that returns an aggregate metric without modifying data.
Attacks that exploit this kind of access
Count documents in a MongoDB collection. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for mongodb_count: 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 Multi-Database MCP Server. Nothing to install.
mongodb_count 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 mongodb_count 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 mongodb_count. 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.
mongodb_count is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). 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 →