Low Risk

get_server_info

Describe the currently exposed MCP surface and deferred areas.

How to control get_server_info ↓

What get_server_info does on GongMun Doctor MCP

AI agents call get_server_info to retrieve information from GongMun Doctor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_server_info needs a policy

This tool purely retrieves and returns information about the server's exposed functionality and limitations. It has no side effects, performs no operations, and cannot affect data or system state. It is a straightforward informational query, placing it firmly in the Read category with low severity since misuse would only result in disclosure of already-known or low-sensitivity metadata about the server itself.

From the tool's definition Tool name 'get_server_info' and description 'Describe the currently exposed MCP surface and deferred areas' indicate a read-only query operation that retrieves metadata about the server's capabilities without modifying, executing, or deleting anything.

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

How to control get_server_info

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_info": {}
  }
}

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

  1. Create a free account and register GongMun Doctor MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_server_info

What does the get_server_info tool do? +

Describe the currently exposed MCP surface and deferred areas. It is categorised as a Read tool in the GongMun Doctor MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_info? +

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

What risk level is get_server_info? +

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

Can I rate-limit get_server_info? +

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

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

get_server_info is provided by the GongMun Doctor MCP server (sinmb79/gongmun-doctor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GongMun Doctor MCP tool call.

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

Free to start. No card required.

10 GongMun Doctor MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.