performance_trace_delete

Delete a captured native performance trace artifact and its metadata.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/performance-trace-delete.md

WHAT IT DOES

What performance_trace_delete does on Claude Mobile

AI agents call performance_trace_delete to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why performance_trace_delete is rated Critical

Irreversibly deletes performance trace artifacts and associated metadata.

From the tool's definition Delete a captured native performance trace artifact and its metadata

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs performance_trace_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_trace_delete, this is the rule to start with:

performance_trace_delete Hidden

performance_trace_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every performance_trace_delete call is checked against it from then on.

FAQ

Questions about performance_trace_delete

What does the performance_trace_delete tool do? +

Delete a captured native performance trace artifact and its metadata. It is categorised as a Destructive tool in the Claude Mobile 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 performance_trace_delete? +

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

What risk level is performance_trace_delete? +

performance_trace_delete 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 performance_trace_delete? +

Yes. Add a rate_limit block to the performance_trace_delete 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 performance_trace_delete completely? +

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

performance_trace_delete is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 214 Claude Mobile tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →