primary_ping
Short reachability + auth check against the user's primary remote device. Returns transport, latency-class info, agent version, lifecycle, ownerEmail, and whether the box's owner matches the caller. Same shape as yaver primary ping --json.
This record as markdown: /tools/io-github-kivanccakmak-yaver/primary-ping.md
What primary_ping does on Yaver
AI agents call primary_ping 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.
Why primary_ping is rated Low
primary_ping retrieves and reports status information about a remote device without modifying, executing operations, or deleting anything. It is purely diagnostic/observational in nature, making it a Read category tool. The low severity reflects that exposing reachability and metadata poses minimal risk even if misused by an untrusted agent.
From the tool's definition Tool description states it performs a 'reachability + auth check' that 'Returns transport, latency-class info, agent version, lifecycle, ownerEmail, and whether the box's owner matches the caller.' The word 'Returns' and the informational nature of the…
Attacks that exploit this kind of access
The rule that runs primary_ping 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 primary_ping, this is the rule to start with:
primary_ping is read-only, so it stays allowed. 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 primary_ping call is checked against it from then on.
Questions about primary_ping
Short reachability + auth check against the user's primary remote device. Returns transport, latency-class info, agent version, lifecycle, ownerEmail, and whether the box's owner matches the caller. Same shape as yaver primary ping --json. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for primary_ping: 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.
primary_ping is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the primary_ping 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 primary_ping. 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.
primary_ping 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.
This server
Across the catalogue