Returns statistics that reflect the use state of a single database.
AI agents call db_stats to retrieve information from Legacy Mongodb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
db_stats retrieves database statistics without side effects. It performs a passive query operation consistent with other Read tools on this server (find, count, explain, etc.). No data is created, modified, deleted, or financial/destructive operations are performed. Low severity due to the non-sensitive nature of database statistics and read-only constraint.
From the tool's definition Tool name 'db_stats' and description 'Returns statistics that reflect the use state of a single database' indicate a read-only retrieval operation. The server description explicitly states 'read-only access' and 'enabling AI models to query databases'.
Attacks that exploit this kind of access
Returns statistics that reflect the use state of a single database. It is categorised as a Read tool in the Legacy Mongodb MCP Server, which means it retrieves data without modifying state.
Register the Legacy Mongodb MCP server in PolicyLayer and add a rule for db_stats: 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 Legacy Mongodb. Nothing to install.
db_stats 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 db_stats 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 db_stats. 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.
db_stats is provided by the Legacy Mongodb MCP server (webxspark/legacy-mongodb-mcp). 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 →