simulator_screenshot

Capture simulator screenshot

Server Xclaude Plugin conorluddy/xclaude-plugin
Category Read
Risk class Low
Parameters 00 required

What simulator_screenshot does on Xclaude Plugin

AI agents call simulator_screenshot to retrieve information from Xclaude Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why simulator_screenshot needs a policy

Taking a screenshot is a passive observation action with no side effects, data modifications, or external operations triggered. It merely captures and returns the current visual state of the simulator. This aligns with the Read category definition of retrieving data with no side effects. Severity is low because screenshot capture poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'simulator_screenshot' and description 'Capture simulator screenshot' indicate a read-only operation that retrieves visual state of a running iOS simulator without modifying any data or state.

Questions about simulator_screenshot

What does the simulator_screenshot tool do? +

Capture simulator screenshot. It is categorised as a Read tool in the Xclaude Plugin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on simulator_screenshot? +

Register the Xclaude Plugin 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 Xclaude Plugin. 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 Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

simulator_screenshot is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.