start-heap-sampling · Debugger MCP Server MCP: Risk & Policy

WHAT IT DOES

What start-heap-sampling does on Debugger MCP Server

AI agents invoke start-heap-sampling 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 start-heap-sampling needs a policy

While not creating, modifying, or deleting data, this tool executes a debugging operation that initiates heap sampling—an active process that affects the application's runtime behavior and resource consumption. It triggers external profiling operations that could impact performance or reveal sensitive information about application internals. This fits the Execute category (runs code/triggers external operations).

From the tool's definition Tool starts heap sampling for memory profiling, which is an active operation that initiates a monitoring/profiling process on the running application.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start-heap-sampling Rate-limited

start-heap-sampling 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": {
    "start-heap-sampling": {
      "limits": [
        {
          "counter": "start-heap-sampling_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 start-heap-sampling

What does the start-heap-sampling tool do? +

Start heap sampling for memory profiling and leak detection. 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 start-heap-sampling? +

Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for start-heap-sampling: 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 start-heap-sampling? +

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

Can I rate-limit start-heap-sampling? +

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

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

start-heap-sampling 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.