get_server_status

THE RISK

Low Risk

Why get_server_status needs a policy

This tool queries internal server state (parsing progress, index statistics) and returns information without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—misuse would only expose metadata about the codebase analysis server itself.

From the tool's definition Tool name 'get_server_status' and description 'Get MCP server status including parsing progress and index stats' indicate read-only retrieval of status and metrics information with no modifications, side effects, or external operations.

Documented attack patterns abuse exactly the kind of access get_server_status gives an agent:

POLICY

How to control get_server_status

PolicyLayer is an MCP gateway — it sits between your AI agents and C++ MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_status": {}
  }
}

get_server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register C++ MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More C++ MCP Server tools

Execute refresh_project Manually refresh/re-parse project files to detect changes Write set_project_directory Set the project directory to analyze (use this first before other commands) Read find_callees Find all functions called by a specific function Read find_callers Find all functions that call a specific function Read find_in_file Search for symbols within a specific file Read get_call_path Find call paths from one function to another Read get_class_hierarchy Get complete inheritance hierarchy for a C++ class Read get_class_info Get detailed information about a specific class

All 14 C++ MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_server_status

What does the get_server_status tool do? +

Get MCP server status including parsing progress and index stats. It is categorised as a Read tool in the C++ MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_status? +

Register the C++ MCP Server MCP server in PolicyLayer and add a rule for 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 C++ MCP Server. Nothing to install.

What risk level is get_server_status? +

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

Can I rate-limit get_server_status? +

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

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

get_server_status is provided by the C++ MCP Server MCP server (kandrwmrtn/cplusplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every C++ MCP Server tool call.

Start from C++ MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →