AI agents call get_simulator_logs to retrieve information from Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing log data from a booted iOS Simulator without creating, modifying, deleting, or executing any operations. It has no side effects beyond querying and returning information. The blast radius is minimal—an AI agent misusing this would only expose logs that may already be accessible through normal debugging channels.
From the tool's definition Tool name 'get_simulator_logs' and description 'Get logs from an iOS Simulator' indicates data retrieval with no modification. The word 'Get' and the read-only nature of log access confirm this is a retrieval operation.
Attacks that exploit this kind of access
Get logs from an iOS Simulator. The simulator must be booted. It is categorised as a Read tool in the Console MCP Server, which means it retrieves data without modifying state.
Register the Console MCP server in PolicyLayer and add a rule for get_simulator_logs: 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 Console. Nothing to install.
get_simulator_logs 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_logs 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_logs. 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_logs is provided by the Console MCP server (rohithgoud30/console-mcp). 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 →