Save current device logs to a file
AI agents use save_device_logs to create or update resources in Xcode Errors MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xcode Errors MCP Server environment.
This tool writes data (device logs) to a file, which is a reversible modification operation. It does not execute arbitrary code, delete data, move money, or perform destructive actions. The severity is low because saving logs has minimal blast radius—it creates files in a controlled manner without affecting system state or other data beyond the log file itself.
From the tool's definition Tool name 'save_device_logs' and description 'Save current device logs to a file' indicate creation/writing of a log file to persistent storage.
Attacks that exploit this kind of access
Save current device logs to a file. It is categorised as a Write tool in the Xcode Errors MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xcode Errors MCP Server MCP server in PolicyLayer and add a rule for save_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.
save_device_logs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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 →