system_doctor

Read system.doctor through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/system-doctor.md

WHAT IT DOES

What system_doctor does on Appaloft

AI agents call system_doctor to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why system_doctor is rated Low

This tool retrieves system diagnostic or status information through the Appaloft application catalog. It has no side effects, does not modify data, and does not execute arbitrary operations. The 'Read' classification is appropriate for diagnostic/informational tools. Severity is low because querying system status information poses minimal risk even if accessed by an unauthorized agent.

From the tool's definition Tool name includes 'system_doctor' and description explicitly states 'Read system.doctor through the Appaloft application operation catalog.' The word 'Read' in the description and the diagnostic nature of 'doctor' indicate information retrieval without…

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs system_doctor safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, 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 Allowed

system_doctor is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "system_doctor": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every system_doctor call is checked against it from then on.

FAQ

Questions about system_doctor

What does the system_doctor tool do? +

Read system.doctor through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on system_doctor? +

Register the Appaloft 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 Appaloft. Nothing to install.

What risk level is system_doctor? +

system_doctor is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit system_doctor? +

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.

How do I block system_doctor completely? +

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.

What MCP server provides system_doctor? +

system_doctor is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →