Read the most recent openchrome doctor diagnostic report from cache. Returns the DoctorReport written by the last
AI agents call oc_doctor_report to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cached diagnostic information about OpenChrome's health status. It performs a query operation with no side effects, data modification, code execution, or destructive capability. The 'Read' category applies as it simply fetches and returns existing diagnostic report data. Severity is low because diagnostic reports contain no sensitive operational data that could cause harm if misused by an agent.
From the tool's definition Tool name 'oc_doctor_report' and description 'Read the most recent openchrome doctor diagnostic report from cache' explicitly indicate a read operation that retrieves diagnostic data without modifying or executing any actions.
Documented attack patterns abuse exactly the kind of access oc_doctor_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for oc_doctor_report:
{
"version": "1",
"default": "deny",
"tools": {
"oc_doctor_report": {}
}
}oc_doctor_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read the most recent openchrome doctor diagnostic report from cache. Returns the DoctorReport written by the last. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_doctor_report: 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 OpenChrome. Nothing to install.
oc_doctor_report 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 oc_doctor_report 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 oc_doctor_report. 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.
oc_doctor_report is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.