New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

yaver_devices

List all registered devices across your account (dev machines, laptops, servers) with online/offline status.

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-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.

Questions about yaver_devices

What does the yaver_devices tool do? +

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.

How do I enforce a policy on yaver_devices? +

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.

What risk level is yaver_devices? +

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

Can I rate-limit yaver_devices? +

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.

How do I block yaver_devices completely? +

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.

What MCP server provides yaver_devices? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.