system.doctor
Core doctor: offline, no optional dependency required.
This record as markdown: /tools/visionmcp/system.doctor.md
What system.doctor does on Visionmcp
AI agents call system.doctor to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why system.doctor is rated Low
A 'doctor' function typically performs diagnostics and reporting on system status—a read-only operation that retrieves information about the system's health or configuration. The 'offline' qualifier and lack of dependency requirements further suggest this is a local diagnostic tool with no side effects. No evidence of write, execution, deletion, or financial operations.
From the tool's definition Tool name 'system.doctor' with description 'Core doctor: offline, no optional dependency required.' suggests a diagnostic or health-check utility that queries system state without modifying it. The word 'doctor' implies analysis/inspection rather than action.
Attacks that exploit this kind of access
The rule that runs system.doctor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system.doctor, this is the rule to start with:
system.doctor is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every system.doctor call is checked against it from then on.
Questions about system.doctor
Core doctor: offline, no optional dependency required. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for system.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 Visionmcp. Nothing to install.
system.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 system.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 system.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.
system.doctor is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue