mcp_get_server_status

Get MongoDB server status information.

SERVERMongo-MCP SOURCE441126098/mongo-mcp

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/441126098-mongo-mcp/mcp-get-server-status.md

WHAT IT DOES

What mcp_get_server_status does on Mongo-MCP

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

RISK

Why mcp_get_server_status is rated Low

This tool retrieves server status and monitoring information without creating, modifying, deleting, or executing operations. It has no side effects and poses minimal risk. The low severity reflects that status information is typically non-sensitive operational metadata, and misuse would only inform an agent rather than cause harm.

From the tool's definition Tool name 'mcp_get_server_status' and description 'Get MongoDB server status information' indicate retrieval of operational metrics and server state without modification. This is a read-only operation that queries server diagnostics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_get_server_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mongo-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_get_server_status, this is the rule to start with:

mcp_get_server_status Allowed

mcp_get_server_status 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": {
    "mcp_get_server_status": {}
  }
}

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

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

FAQ

Questions about mcp_get_server_status

What does the mcp_get_server_status tool do? +

Get MongoDB server status information. It is categorised as a Read tool in the Mongo-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mcp_get_server_status? +

Register the Mongo MCP server in PolicyLayer and add a rule for mcp_get_server_status: 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 Mongo-MCP. Nothing to install.

What risk level is mcp_get_server_status? +

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

Can I rate-limit mcp_get_server_status? +

Yes. Add a rate_limit block to the mcp_get_server_status 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 mcp_get_server_status completely? +

Set action: deny in the PolicyLayer policy for mcp_get_server_status. 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 mcp_get_server_status? +

mcp_get_server_status is provided by the Mongo MCP server (441126098/mongo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mongo, and thousands of servers like it.

This server

All 30 Mongo tools →

Across the catalogue

server_status on 010 Editor →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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