simulator_screenshot

Take a screenshot from iOS simulator.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/simulator-screenshot.md

WHAT IT DOES

What simulator_screenshot does on Yaver

AI agents call simulator_screenshot 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.

Parameter	Type	Required	Description
`device`	string	—	Device ID (default: booted)

Parameters from the server's own tool schema.

RISK

Why simulator_screenshot is rated Low

Screenshots are informational reads from the simulator's display buffer. They do not modify, delete, or execute anything. The tool captures visual state without triggering application logic or external operations. Risk is minimal; misuse would only expose visible UI state to the agent.

From the tool's definition Tool description states 'Take a screenshot from iOS simulator' — a pure data retrieval operation with no side effects, no code execution, and no modifications to state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs simulator_screenshot 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 simulator_screenshot, this is the rule to start with:

simulator_screenshot Allowed

simulator_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simulator_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every simulator_screenshot call is checked against it from then on.

FAQ

Questions about simulator_screenshot

What does the simulator_screenshot tool do? +

Take a screenshot from iOS simulator. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does simulator_screenshot accept? +

simulator_screenshot accepts 1 parameter: device. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on simulator_screenshot? +

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

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

Can I rate-limit simulator_screenshot? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

browser_screenshot on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →