force_gc · Mcp Rn Devtools MCP: Risk & Policy

WHAT IT DOES

What force_gc does on Mcp Rn Devtools

AI agents invoke force_gc to trigger actions in Mcp Rn Devtools. 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_gc needs a policy

Forcing garbage collection is an active runtime operation that triggers the JS engine to reclaim memory. It has real side effects on the running application (pausing execution, freeing memory, potentially invalidating object references), making it Execute. It is not purely read-only, but also not destructive in an irreversible data-loss sense.

From the tool's definition 'Force garbage collection' — actively triggers a GC cycle in the running app, an external operation that directly affects the app's runtime memory state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

force_gc Rate-limited

force_gc 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_gc": {
      "limits": [
        {
          "counter": "force_gc_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 Mcp Rn Devtools, so you can run agents against it safely.

FAQ

Questions about force_gc

What does the force_gc tool do? +

Force garbage collection and return before/after heap memory comparison. It is categorised as a Execute tool in the Mcp Rn Devtools 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_gc? +

Register the Mcp Rn Devtools MCP server in PolicyLayer and add a rule for force_gc: 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 Mcp Rn Devtools. Nothing to install.

What risk level is force_gc? +

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

Can I rate-limit force_gc? +

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

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

force_gc is provided by the Mcp Rn Devtools MCP server (pablonortiz/mcp-rn-devtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.