Get logs from a specific connected iOS device or simulator
AI agents call get_device_logs to retrieve information from Xcode Errors MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing log data from a device or simulator. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The retrieval of logs poses minimal security risk in a development context.
From the tool's definition Tool name is 'get_device_logs' and description states 'Get logs from a specific connected iOS device or simulator' — this retrieves log data without modifying or executing operations.
Attacks that exploit this kind of access
Get logs from a specific connected iOS device or simulator. It is categorised as a Read tool in the Xcode Errors MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Xcode Errors MCP Server MCP server in PolicyLayer and add a rule for get_device_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 Xcode Errors MCP Server. Nothing to install.
get_device_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_device_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_device_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_device_logs is provided by the Xcode Errors MCP Server MCP server (nazufel/xcode-errors-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 →