mongosh-stats

Gets MongoDB database statistics (collections, objects, data size, storage, indexes) via mongosh.

SERVERTest SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-pare-test/mongosh-stats.md

WHAT IT DOES

What mongosh-stats does on Test

AI agents call mongosh-stats to retrieve information from Test without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mongosh-stats is rated Low

This tool performs read-only queries against MongoDB to gather database metadata and statistics. It does not modify data (not Write), delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial).

From the tool's definition Retrieves MongoDB database statistics (collections, objects, data size, storage, indexes) via mongosh; no modification, deletion, or execution of code—purely statistical queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mongosh-stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Test, 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 Allowed

mongosh-stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mongosh-stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every mongosh-stats call is checked against it from then on.

FAQ

Questions about mongosh-stats

What does the mongosh-stats tool do? +

Gets MongoDB database statistics (collections, objects, data size, storage, indexes) via mongosh. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mongosh-stats? +

Register the Test 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 Test. Nothing to install.

What risk level is mongosh-stats? +

mongosh-stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mongosh-stats? +

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.

How do I block mongosh-stats completely? +

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.

What MCP server provides mongosh-stats? +

mongosh-stats is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Test, and thousands of servers like it.

This server

All 202 Test tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →