diagnose
Run the yaver self-check (binary paths, running procs, ports, auth state, workspace manifest, systemd unit, runtime deps). Returns the event list and final summary. Equivalent to yaver diagnose.
This record as markdown: /tools/io-github-kivanccakmak-yaver/diagnose.md
What diagnose does on Yaver
AI agents invoke diagnose 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
fix | boolean | — | |
only | array | — | |
skip | array | — |
Parameters from the server's own tool schema.
Why diagnose is rated High
The tool runs an external command (`yaver diagnose`) that actively interrogates system state including processes, ports, and systemd units. This is execution of an external operation, not a passive read. While it appears read-only in intent, it triggers real process execution with potential side effects on system inspection and auth state queries, placing it firmly in Execute.
From the tool's definition 'Run the yaver self-check' and 'Equivalent to `yaver diagnose`' — executes an external CLI process that inspects binary paths, running procs, ports, auth state, workspace manifest, systemd unit, and runtime deps.
Attacks that exploit this kind of access
The rule that runs diagnose 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 diagnose, this is the rule to start with:
diagnose 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 diagnose call is checked against it from then on.
Questions about diagnose
Run the yaver self-check (binary paths, running procs, ports, auth state, workspace manifest, systemd unit, runtime deps). Returns the event list and final summary. Equivalent to yaver diagnose. 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.
diagnose accepts 3 parameters: fix, only, skip. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for diagnose: 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.
diagnose 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 diagnose 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 diagnose. 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.
diagnose 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