mongosh-stats
Gets MongoDB database statistics (collections, objects, data size, storage, indexes) via mongosh.
This record as markdown: /tools/io-github-dave-london-http/mongosh-stats.md
What mongosh-stats does on Http
AI agents call mongosh-stats to retrieve information from Http without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mongosh-stats is rated Low
This tool performs read-only queries against MongoDB using mongosh to gather statistics and metadata. It does not create, modify, delete, or execute arbitrary operations—it only queries and retrieves database information.
From the tool's definition mongosh-stats retrieves MongoDB database statistics including collections, objects, data size, storage, and indexes. This is explicitly a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs mongosh-stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Http, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mongosh-stats, this is the rule to start with:
mongosh-stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Http, apply this rule, and every mongosh-stats call is checked against it from then on.
Questions about mongosh-stats
Gets MongoDB database statistics (collections, objects, data size, storage, indexes) via mongosh. It is categorised as a Read tool in the Http MCP Server, which means it retrieves data without modifying state.
Register the Http MCP server in PolicyLayer and add a rule for mongosh-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 Http. Nothing to install.
mongosh-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 mongosh-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 mongosh-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.
mongosh-stats is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue