Low Risk

orgo_doctor

Probe MCP server health. Returns auth source, API reachability, and latency.

How to control orgo_doctor ↓

What orgo_doctor does on Orgo MCP Server

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

Low Risk

Why orgo_doctor needs a policy

This tool only reads and returns diagnostic information (auth source, API reachability, latency) without modifying any state or triggering side effects. It is a health-check/probe operation with no write or destructive capability.

From the tool's definition Probe MCP server health. Returns auth source, API reachability, and latency.

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

How to control orgo_doctor

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

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

orgo_doctor 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 Orgo MCP Server — 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 orgo_doctor

What does the orgo_doctor tool do? +

Probe MCP server health. Returns auth source, API reachability, and latency. It is categorised as a Read tool in the Orgo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on orgo_doctor? +

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

What risk level is orgo_doctor? +

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

Can I rate-limit orgo_doctor? +

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

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

orgo_doctor is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orgo MCP Server tool call.

Start from Orgo MCP Server, 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.

28 Orgo MCP Server 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.