AI agents invoke launch_app to trigger actions in Shotter. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (app launch) whose effects depend on which app is specified. Although launching a benign app may be harmless, an agent could launch apps with side effects (malware, credential stealers, payment apps, or apps that modify device state). The impact is contained to the simulator, but the ability to trigger arbitrary application execution qualifies as Execute risk.
From the tool's definition 'Launch an app by its bundle identifier' — directly triggers application execution on an iOS Simulator, which is a code/process execution action.
Attacks that exploit this kind of access
Launch an app by its bundle identifier. It is categorised as a Execute tool in the Shotter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shotter MCP server in PolicyLayer and add a rule for launch_app: 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.
launch_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the launch_app 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 launch_app. 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.
launch_app 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 →