performance_trace_stop

Finalize an active performance trace, store the native artifact with mode 0600 and 24-hour TTL, and return a bounded agent-readable summary plus checksum.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What performance_trace_stop does on Claude Mobile

AI agents invoke performance_trace_stop to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why performance_trace_stop is rated High

Stops a trace and writes a file artifact; triggers external operation with side effects.

From the tool's definition Finalize active performance trace, store native artifact, return summary

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs performance_trace_stop 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_stop, this is the rule to start with:

performance_trace_stop Rate-limited

performance_trace_stop stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "performance_trace_stop": {
      "limits": [
        {
          "counter": "performance_trace_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_stop call is checked against it from then on.

FAQ

Questions about performance_trace_stop

What does the performance_trace_stop tool do? +

Finalize an active performance trace, store the native artifact with mode 0600 and 24-hour TTL, and return a bounded agent-readable summary plus checksum. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on performance_trace_stop? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for performance_trace_stop: 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_stop? +

performance_trace_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit performance_trace_stop? +

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

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

performance_trace_stop 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 → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →