entire_doctor · Entire MCP: Risk & Policy

WHAT IT DOES

What entire_doctor does on Entire

AI agents invoke entire_doctor to trigger actions in Entire. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why entire_doctor needs a policy

This tool executes diagnostic operations (likely shell commands or API calls) to inspect system and repository state. While diagnostics are typically non-destructive reads, the act of 'running' diagnostics constitutes Execute rather than Read, as it triggers external operations and may have side effects (logging, temporary file creation, system probing).

From the tool's definition Tool name 'entire_doctor' and description 'Run diagnostics on the Entire installation and current repo setup' indicates execution of diagnostic operations.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

entire_doctor Rate-limited

entire_doctor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "entire_doctor": {
      "limits": [
        {
          "counter": "entire_doctor_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Entire, so you can run agents against it safely.

FAQ

Questions about entire_doctor

What does the entire_doctor tool do? +

Run diagnostics on the Entire installation and current repo setup. Uses \. It is categorised as a Execute tool in the Entire MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on entire_doctor? +

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

What risk level is entire_doctor? +

entire_doctor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit entire_doctor? +

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

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

entire_doctor is provided by the Entire MCP server (jurislm/entire-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.