This record as markdown: /tools/io-github-kivanccakmak-yaver/ping.md
What ping does on Yaver
AI agents invoke ping 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 |
|---|---|---|---|
host | string | Yes | Host to ping |
count | integer | — | Number of pings (default: 4) |
Parameters from the server's own tool schema.
Why ping is rated High
Pinging a host is an active network operation that sends packets to an external system. It is not purely a read/query of local data; it executes an outbound network action whose effects depend on the target argument. Misuse could enable reconnaissance or be used to probe internal network hosts.
From the tool's definition 'Ping a host' — triggers an external network operation (ICMP or similar probe) against a remote target
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs 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 ping, this is the rule to start with:
ping 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 ping call is checked against it from then on.
Questions about ping
Ping a host. 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.
ping accepts 2 parameters: host, count. Required: host. 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 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.
ping 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 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 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.
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.
Across the catalogue