yaver_devices
List all registered devices across your account (dev machines, laptops, servers) with online/offline status.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-devices.md
What yaver_devices does on Yaver
AI agents call yaver_devices 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 yaver_devices is rated Low
This tool performs device enumeration and status checking—a read operation with no side effects. It queries existing data about devices but does not create, modify, delete, execute code, or commit financial actions. The blast radius of misuse is low: an agent listing devices gains awareness of infrastructure but cannot directly harm systems.
From the tool's definition Tool name 'yaver_devices' and description 'List all registered devices across your account... with online/offline status' indicates a read-only query operation that retrieves device inventory and status information without modification or side effects.
Attacks that exploit this kind of access
The rule that runs yaver_devices 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_devices, this is the rule to start with:
yaver_devices 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 yaver_devices call is checked against it from then on.
Questions about yaver_devices
List all registered devices across your account (dev machines, laptops, servers) with online/offline status. 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 yaver_devices: 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_devices 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 yaver_devices 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_devices. 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_devices 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