yaver_doctor

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-doctor.md

WHAT IT DOES

What yaver_doctor does on Yaver

AI agents invoke yaver_doctor to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why yaver_doctor is rated High

Executes diagnostic operations across system components; results determine development environment state and readiness.

From the tool's definition Run comprehensive system health check, auth, runners, API-key readiness, tunnels

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs yaver_doctor safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For yaver_doctor, this is the rule to start with:

yaver_doctor Rate-limited

yaver_doctor stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_doctor": {
      "limits": [
        {
          "counter": "yaver_doctor_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about yaver_doctor

What does the yaver_doctor tool do? +

Run a comprehensive system health check — auth, agent, runners, provider/API-key readiness, OS-specific development tools, relay servers, tunnels, network, and tmux sessions. Like 'yaver doctor' in the GUI. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on yaver_doctor? +

Register the Yaver MCP server in PolicyLayer and add a rule for yaver_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 Yaver. Nothing to install.

What risk level is yaver_doctor? +

yaver_doctor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit yaver_doctor? +

Yes. Add a rate_limit block to the yaver_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 yaver_doctor completely? +

Set action: deny in the PolicyLayer policy for yaver_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 yaver_doctor? +

yaver_doctor is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →