// SCAN REPORT

Shotter

13 tools. 7 can modify or destroy data without limits.

7 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

7 can modify or destroy data

6 read-only

13 tools total

Community server · catalogue entry verified 04/07/2026

How to control Shotter ↓

TOOL MAP

What Shotter exposes to your agents

Read (6) Write / Execute (7) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Shotter tools

Execute · High launch_app This tool executes an external operation (app launch) whose effects depend on which app is specified. Execute · Medium open_simulator This tool launches an external application (iOS Simulator), which is an execution action that triggers an external operation. Execute · Medium select_device This tool triggers an external operation (booting an iOS Simulator and setting it as active), which is a side-effecting action that changes system state. Execute · Medium ui_swipe This tool triggers an external UI interaction (swipe gesture) on the iOS Simulator, causing side effects that depend on the arguments (direction, coordinates, target element).

7 of Shotter's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Shotter

PolicyLayer is an MCP gateway — it sits between your AI agents and Shotter, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "step_complete": {
    "limits": [
      {
        "counter": "step_complete_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_devices": {
    "limits": [
      {
        "counter": "list_devices_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Shotter — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SHOTTER →

Instant setup, no code required.

FULL CATALOGUE

All 13 Shotter tools

EXECUTE 6 tools

Execute launch_app Launch an app by its bundle identifier. Execute open_simulator Open the iOS Simulator application. Use this if the simulator is not already running. Execute select_device Boot an iOS simulator and set it as the active device. Uses fuzzy matching for device names. Execute ui_swipe Perform a swipe gesture on the iOS Simulator screen. Use this to scroll content or perform swipe actions. Execute ui_tap Tap on the screen at specific coordinates in the iOS Simulator. Use this to tap buttons, icons, or any interac Execute ui_type Type text into the iOS Simulator. The text field must already be focused. Only supports ASCII printable charac

WRITE 1 tools

Write step_complete Signal that the current navigation step goal has been achieved. Call this when you have successfully completed

READ 6 tools

Read list_devices List available iOS simulator devices. Returns device names, UDIDs, states, and iOS versions. Read list_workflows List available workflow YAML files in a directory. Read load_workflow Load and parse a workflow YAML file. Returns steps, devices, and configuration. Read screenshot Save a high-quality screenshot to a file. Use this when you need to save a screenshot for the user. Read ui_describe_all Get accessibility information for all UI elements currently visible on screen. Returns element labels, types, Read ui_view Capture a compressed screenshot of the current simulator screen for visual analysis. Use this to see what

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Shotter

How do I prevent bulk modifications through Shotter? +

The Shotter server has 1 write tools including step_complete. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Shotter.

How many tools does the Shotter MCP server expose? +

13 tools across 3 categories: Execute, Read, Write. 6 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Shotter? +

Register the Shotter MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Shotter tool call.

Deterministic rules across all 13 Shotter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SHOTTER →

Instant setup, no code required.

13 Shotter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.