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.
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
Attacks that exploit this kind of access
The rule that runs real_device_probe 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 real_device_probe, this is the rule to start with:
real_device_probe 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 real_device_probe call is checked against it from then on.
Questions about 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. 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 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.
real_device_probe 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 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.
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.
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.
This server
Across the catalogue