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

real_device_probe

List physical Android phones/tablets attached to this Yaver host and operation-test screen capture. Reports whether scrcpy is installed, but uses the same ADB/WebRTC runtime contract as Studio; follow with runtime_create, runtime_frame and runtime_control for a closed-loop automation test.

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/real-device-probe.md

What real_device_probe does on Yaver

AI agents call real_device_probe 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 real_device_probe is rated Low

Probes attached devices and tests screen capture; reads device state without persistent modification.

From the tool's definition List physical Android phones/tablets... operation-test screen capture

Questions about real_device_probe

What does the real_device_probe tool do? +

List physical Android phones/tablets attached to this Yaver host and operation-test screen capture. Reports whether scrcpy is installed, but uses the same ADB/WebRTC runtime contract as Studio; follow with runtime_create, runtime_frame and runtime_control for a closed-loop automation test. 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 real_device_probe? +

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

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

Can I rate-limit real_device_probe? +

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

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

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

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