Gets information about the currently booted iOS simulator.
AI agents call get_simulator_info to retrieve information from MCP Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about an iOS simulator's configuration and status. It performs no write operations, does not execute code or scripts, does not delete data, and has no financial implications. The read-only nature and informational output place it squarely in the Read category with low severity, as misuse would only expose simulator details rather than cause system changes or damage.
From the tool's definition Tool name 'get_simulator_info' and description 'Gets information about the currently booted iOS simulator' indicate a query-only operation that retrieves simulator state/metadata without modification or execution of commands.
Attacks that exploit this kind of access
Gets information about the currently booted iOS simulator. It is categorised as a Read tool in the MCP Connect MCP Server, which means it retrieves data without modifying state.
Register the MCP Connect MCP server in PolicyLayer and add a rule for get_simulator_info: 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 MCP Connect. Nothing to install.
get_simulator_info 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 get_simulator_info 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 get_simulator_info. 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.
get_simulator_info is provided by the MCP Connect MCP server (plaintest/mcp-connect). 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 →