AI agents invoke launch_app_logs_sim to trigger actions in Sl Test. 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 code/operations (app launch in a simulator) whose effects depend on which app is specified and how the simulator responds. It is not merely reading data (though log capture is a side effect), but actively running an external process.
From the tool's definition The tool name explicitly states 'launch_app' and description says 'Launches an app in an iOS simulator and captures its logs.' Launching an application is an executable action that triggers external operations (simulator startup, app invocation).
Attacks that exploit this kind of access
Launches an app in an iOS simulator and captures its logs. It is categorised as a Execute tool in the Sl Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sl Test MCP server in PolicyLayer and add a rule for launch_app_logs_sim: 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 Sl Test. Nothing to install.
launch_app_logs_sim 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_logs_sim 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_logs_sim. 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_logs_sim is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). 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 →