Read-only, manifest-only sanity check. Returns a JSON object with schema status, identity fields, driver summary, HITL gates, E-stop config, and registration status. This is cheaper + safer than the full \
AI agents call doctor_summary to retrieve information from Robot Md without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports status information from a robot manifest in read-only mode. It has no side effects, makes no changes to data, and does not execute commands. The manifest-only scope and explicit 'read-only' designation confirm it is a retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition "Read-only, manifest-only sanity check. Returns a JSON object with schema status, identity fields, driver summary, HITL gates, E-stop config, and registration status." The tool performs query/inspection of manifest data with no modification, deletion, or…
Attacks that exploit this kind of access
Read-only, manifest-only sanity check. Returns a JSON object with schema status, identity fields, driver summary, HITL gates, E-stop config, and registration status. This is cheaper + safer than the full \. It is categorised as a Read tool in the Robot Md MCP Server, which means it retrieves data without modifying state.
Register the Robot Md MCP server in PolicyLayer and add a rule for doctor_summary: 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 Robot Md. Nothing to install.
doctor_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the doctor_summary 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.
Set action: deny in the PolicyLayer policy for doctor_summary. 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.
doctor_summary is provided by the Robot Md MCP server (robotregistryfoundation/robot-md-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →