yaver_doctor
Run a comprehensive system health check — auth, agent, runners, relay servers, tunnels, network, tmux sessions. Like 'yaver doctor' on the CLI.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-doctor.md
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.
Why yaver_doctor is rated High
The tool executes a multi-faceted system diagnostic that checks infrastructure state (runners, relay servers, tunnels, network status) and session management (tmux sessions). While read-only in intent, it triggers external operations and system probes whose side effects depend on system state.
From the tool's definition Tool performs 'comprehensive system health check' including auth, runners, relay servers, tunnels, network, and tmux sessions — these are diagnostic/monitoring operations that probe system state and execute inspection routines across multiple infrastructure…
Attacks that exploit this kind of access
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 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.
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.
Questions about yaver_doctor
Run a comprehensive system health check — auth, agent, runners, relay servers, tunnels, network, tmux sessions. Like 'yaver doctor' on the CLI. 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.
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.
yaver_doctor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Yaver, and thousands of servers like it.
Across the catalogue