cleanup_traces

THE RISK

Critical Risk

Why cleanup_traces needs a policy

This tool permanently removes trace files without recovery options. While trace data is developer diagnostic output (lower blast radius than production data), the irreversible deletion of performance profiling results that may be needed for regression analysis or compliance justifies 'Destructive' classification and 'high' severity.

From the tool's definition The tool description explicitly states it can 'delete .trace bundles', which is irreversible data removal. The term 'garbage collector' combined with 'Preview or delete' confirms destructive capability.

Documented attack patterns abuse exactly the kind of access cleanup_traces gives an agent:

POLICY

How to control cleanup_traces

PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeTraceMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanup_traces:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cleanup_traces"
  ]
}

cleanup_traces disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register XcodeTraceMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More XcodeTraceMCP tools

Execute profile_running_app Record an app once with a profiling preset and return one combined report. Prefer attach-b Execute track_running_app Record one explicit Instruments template. Use this when the user names a template such as Read analyze_trace Analyze an Xcode Instruments trace file for performance bottlenecks and generate recommend Read check_xctrace Check if xctrace is available and get version information Read compare_traces Compare two trace files to detect performance regressions or improvements Read list_devices List all available devices (simulators and real devices) for profiling Read list_templates List all available Instruments templates on this system

All 8 XcodeTraceMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in XcodeTraceMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cleanup_traces

What does the cleanup_traces tool do? +

Trace garbage collector. Preview or delete .trace bundles after the user is done inspecting profiling results. It is categorised as a Destructive tool in the XcodeTraceMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_traces? +

Register the XcodeTrace MCP server in PolicyLayer and add a rule for cleanup_traces: 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 XcodeTraceMCP. Nothing to install.

What risk level is cleanup_traces? +

cleanup_traces is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_traces? +

Yes. Add a rate_limit block to the cleanup_traces 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.

How do I block cleanup_traces completely? +

Set action: deny in the PolicyLayer policy for cleanup_traces. 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.

What MCP server provides cleanup_traces? +

cleanup_traces is provided by the XcodeTrace MCP server (jamesrochabrun/xcodetracemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every XcodeTraceMCP tool call.

Start from XcodeTraceMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →