Count documents in MongoDB collection
AI agents call mongodb-count to retrieve information from NestJS MongoDB 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 retrieves statistics about a collection without side effects, insertions, deletions, or modifications. This aligns with the Read category for data retrieval operations. Severity is low because misuse poses minimal risk—an agent could at worst cause performance issues through repeated counts on large collections, but no data loss or financial harm is possible.
From the tool's definition Tool name 'mongodb-count' and description 'Count documents in MongoDB collection' indicate a query operation that retrieves aggregate information without modifying data.
Attacks that exploit this kind of access
Count documents in MongoDB collection. It is categorised as a Read tool in the NestJS MongoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NestJS MongoDB 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 NestJS MongoDB 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 NestJS MongoDB MCP Server MCP server (jovicon/nestjs-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 →