AI agents call list_devices to retrieve information from Shotter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available simulator devices without modifying, executing, or deleting anything. It is a straightforward read operation that gathers state information. While the broader server enables automation of iOS interactions, this specific tool is limited to enumeration and retrieval. Low severity because misuse would only expose simulator metadata, not cause harm to applications or data.
From the tool's definition Tool description states it 'List available iOS simulator devices' and 'Returns device names, UDIDs, states, and iOS versions' — purely a query operation with no side effects.
Attacks that exploit this kind of access
List available iOS simulator devices. Returns device names, UDIDs, states, and iOS versions. It is categorised as a Read tool in the Shotter MCP Server, which means it retrieves data without modifying state.
Register the Shotter MCP server in PolicyLayer and add a rule for list_devices: 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 Shotter. Nothing to install.
list_devices 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 list_devices 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 list_devices. 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.
list_devices is provided by the Shotter MCP server (nathanstitt/shotter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →