stop-cpu-profiling · Debugger MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop-cpu-profiling does on Debugger MCP Server

AI agents invoke stop-cpu-profiling to trigger actions in Debugger MCP Server. 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.

WHY IT NEEDS A POLICY

Why stop-cpu-profiling needs a policy

This tool both halts an active CPU profiling session in the browser/runtime and retrieves the resulting profile data. Stopping a profiling session is an external operation that changes the state of the debugging environment. While it has a read component (fetching flame graph data), the primary action is executing a control operation against a live profiling session.

From the tool's definition 'Stop CPU profiling and get the profile data with flame graph' — triggers an external operation (stopping an active profiling session) and retrieves resulting profile data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop-cpu-profiling Rate-limited

stop-cpu-profiling 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": {
    "stop-cpu-profiling": {
      "limits": [
        {
          "counter": "stop-cpu-profiling_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Debugger MCP Server, so you can run agents against it safely.

FAQ

Questions about stop-cpu-profiling

What does the stop-cpu-profiling tool do? +

Stop CPU profiling and get the profile data with flame graph. It is categorised as a Execute tool in the Debugger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop-cpu-profiling? +

Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for stop-cpu-profiling: 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 Debugger MCP Server. Nothing to install.

What risk level is stop-cpu-profiling? +

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

Can I rate-limit stop-cpu-profiling? +

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

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

stop-cpu-profiling is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.