This record as markdown: /tools/io-github-kivanccakmak-yaver/emulators.md
What emulators does on Yaver
AI agents call emulators 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 emulators is rated Low
This tool retrieves and enumerates existing Android Virtual Device (AVD) emulator configurations. Listing is a read-only operation with no side effects, data modification, or external operations triggered. The blast radius of misuse is minimal - an attacker gains only visibility into available emulator configurations on the local development machine.
From the tool's definition Tool name is 'emulators' and description states 'List Android emulators (AVDs)' - a pure query operation that retrieves information without modification.
Attacks that exploit this kind of access
The rule that runs emulators 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 emulators, this is the rule to start with:
emulators 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 emulators call is checked against it from then on.
Questions about emulators
List Android emulators (AVDs). 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 emulators: 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.
emulators 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 emulators 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 emulators. 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.
emulators 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