Runs a practical LocalWP health check for the selected site, including site resolution, Local tooling, probes, and log availability.
AI agents call local_doctor to retrieve information from LocalWP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs health checks and diagnostics: resolving site configuration, checking Local tooling availability, running probes, and checking log availability. These are all read/query operations with no side effects. No data is created, modified, deleted, or executed beyond inspection queries.
From the tool's definition 'Runs a practical LocalWP health check' and 'probes, and log availability' — diagnostic/read-only operations checking site resolution, tooling, and logs
Attacks that exploit this kind of access
Runs a practical LocalWP health check for the selected site, including site resolution, Local tooling, probes, and log availability. It is categorised as a Read tool in the LocalWP MCP MCP Server, which means it retrieves data without modifying state.
Register the LocalWP MCP server in PolicyLayer and add a rule for local_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 LocalWP MCP. Nothing to install.
local_doctor 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 local_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.
Set action: deny in the PolicyLayer policy for local_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.
local_doctor is provided by the LocalWP MCP server (kazimshah39/localwp-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 →