cdp.performance.trace.stop

SERVERPixi Inspector SOURCEpixi-inspector-mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pixi-inspector-mcp/cdp.performance.trace.stop.md

WHAT IT DOES

What cdp.performance.trace.stop does on Pixi Inspector

AI agents use cdp.performance.trace.stop to create or update resources in Pixi Inspector, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pixi Inspector environment.

Parameter	Type	Required	Description
`tabId`	integer	—	Legacy: a bare tab id, resolved inside the browser this session is already working with. Prefer `target`, which is unambiguous across browsers.
`target`	string	—	Drive a specific tab: a target id like "b7a3c1#487" from status/use_target/CHOOSE_TARGET. Omit to use this session's chosen tab (or the only available one). Pas
`frameId`	integer	—	Escape hatch: drive a specific FRAME of the tab (0 is the top frame). Normally unnecessary — the extension picks the frame running the game (canvas owner first,

Parameters from the server's own tool schema.

RISK

Why cdp.performance.trace.stop is rated Medium

An AI agent can call cdp.performance.trace.stop faster than any human can review: one bad instruction and it creates or modifies resources in Pixi Inspector by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cdp.performance.trace.stop safely

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

cdp.performance.trace.stop Rate-limited

cdp.performance.trace.stop stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cdp.performance.trace.stop": {
      "limits": [
        {
          "counter": "cdp.performance.trace.stop_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every cdp.performance.trace.stop call is checked against it from then on.

FAQ

Questions about cdp.performance.trace.stop

What does the cdp.performance.trace.stop tool do? +

Ends the held tracing session, writes the FULL raw trace JSON to a temp file (loadable in perfetto / chrome://tracing) and returns ONLY its path plus a bounded summary { durationMs, totalEvents, eventsByCategory, topLongTasks }. durationMs spans the first to the last timed event (metadata events are ignored). The raw trace is never returned through MCP; trace files older than 24 h are deleted on the next write. CDP_NO_SESSION if no trace was started. Acts only on the session of the tab this call resolves to; a session held by another tab answers CDP_NO_SESSION naming that tab and is left untouched. It is categorised as a Write tool in the Pixi Inspector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does cdp.performance.trace.stop accept? +

cdp.performance.trace.stop accepts 3 parameters: tabId, target, frameId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cdp.performance.trace.stop? +

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for cdp.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 Pixi Inspector. Nothing to install.

What risk level is cdp.performance.trace.stop? +

cdp.performance.trace.stop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cdp.performance.trace.stop? +

Yes. Add a rate_limit block to the cdp.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 cdp.performance.trace.stop completely? +

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

cdp.performance.trace.stop is provided by the Pixi Inspector MCP server (pixi-inspector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pixi Inspector, and thousands of servers like it.

This server

All 63 Pixi Inspector tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →