This record as markdown: /tools/io-github-kivanccakmak-yaver/simulators.md
What simulators does on Yaver
AI agents call simulators 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 simulators is rated Low
This tool performs a read-only operation that enumerates iOS simulators. It retrieves and displays configuration or status data with no side effects, no code execution, no data modification, and no destructive operations. The only potential risk is information disclosure about available development environments, which is minimal in a local dev context.
From the tool's definition 'List iOS simulators' - a query operation that retrieves information about available simulators without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs simulators 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 simulators, this is the rule to start with:
simulators 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 simulators call is checked against it from then on.
Questions about simulators
List iOS simulators. 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 simulators: 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.
simulators 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 simulators 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 simulators. 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.
simulators 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