force-garbage-collection · Debugger MCP Server MCP

WHAT IT DOES

What force-garbage-collection does on Debugger MCP Server

AI agents invoke force-garbage-collection 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 force-garbage-collection needs a policy

Forcing garbage collection is an external runtime operation that triggers the V8 (or equivalent) garbage collector, affecting application memory state. It is not a simple read, nor does it irreversibly delete user data, but it executes a privileged runtime action that can affect application performance and behavior. Misuse could cause performance disruption or mask memory issues.

From the tool's definition 'Force garbage collection to free memory' — actively triggers a runtime operation (GC cycle) in the browser/Node.js process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

force-garbage-collection Rate-limited

force-garbage-collection 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": {
    "force-garbage-collection": {
      "limits": [
        {
          "counter": "force-garbage-collection_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 force-garbage-collection

What does the force-garbage-collection tool do? +

Force garbage collection to free memory and analyze memory leaks. 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 force-garbage-collection? +

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

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

Can I rate-limit force-garbage-collection? +

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

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

force-garbage-collection 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.