run_doctor · ROS 2 MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_doctor does on ROS 2 MCP Server

AI agents invoke run_doctor to trigger actions in ROS 2 MCP Server. 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 run_doctor needs a policy

The 'run_' prefix combined with 'doctor' (a ROS 2 diagnostic tool) indicates this executes external operations whose effects depend on runtime state and system configuration. ROS doctor commands can trigger node checks, network diagnostics, and system-level operations. Classified as Execute rather than Read because 'run' implies active invocation of operations beyond passive data retrieval.

From the tool's definition Tool name 'run_doctor' in ROS 2 context indicates execution of diagnostic/maintenance operations. ROS 2 'doctor' commands run system checks and can execute arbitrary diagnostic code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_doctor Rate-limited

run_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": {
    "run_doctor": {
      "limits": [
        {
          "counter": "run_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 ROS 2 MCP Server, so you can run agents against it safely.

FAQ

Questions about run_doctor

What does the run_doctor tool do? +

run_doctor. It is categorised as a Execute tool in the ROS 2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_doctor? +

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

What risk level is run_doctor? +

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

Can I rate-limit run_doctor? +

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

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

run_doctor is provided by the ROS 2 MCP Server MCP server (ranch-hand-robotics/rde-mcp-ros-2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.