yaver_health_deep

SERVERYaver SOURCEyaver-cli

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/io-github-kivanccakmak-yaver/yaver-health-deep.md

WHAT IT DOES

What yaver_health_deep does on Yaver

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

RISK

Why yaver_health_deep is rated Low

This tool queries and reports health status of various subsystems without making any changes. It provides diagnostic information to help callers decide recovery actions, but does not itself execute those actions, modify state, or trigger external operations. It is a pure diagnostic/monitoring query, fitting the Read category.

From the tool's definition Tool description explicitly states it 'Returns graduated recovery hints' and lists informational subsystem checks: 'agent HTTP mux, tmux availability, runner keeper, per-session status, remote-runtime sessions, WebRTC pump liveness.' No modifications,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs yaver_health_deep 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_health_deep, this is the rule to start with:

yaver_health_deep Allowed

yaver_health_deep 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": {
    "yaver_health_deep": {}
  }
}

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

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

FAQ

Questions about yaver_health_deep

What does the yaver_health_deep tool do? +

Per-subsystem actionable health: agent HTTP mux, tmux availability, runner keeper + per-session status (idle / stalled / draining), remote-runtime sessions + WebRTC pump liveness. Returns graduated recovery hints so callers can decide the escalation. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on yaver_health_deep? +

Register the Yaver MCP server in PolicyLayer and add a rule for yaver_health_deep: 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_health_deep? +

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

Can I rate-limit yaver_health_deep? +

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

Set action: deny in the PolicyLayer policy for yaver_health_deep. 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_health_deep? +

yaver_health_deep 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 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

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