fire_reactor · Baselings MCP: Risk & Policy

WHAT IT DOES

What fire_reactor does on Baselings

AI agents invoke fire_reactor to trigger actions in Baselings. 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 fire_reactor needs a policy

This tool executes an on-chain operation that triggers a multi-step automated cycle (fee collection, token burning, liquidity deepening, upstream distribution). While it is described as 'permissionless' and relatively cheap (~$0.01 gas), it irreversibly burns tokens and modifies on-chain state.

From the tool's definition Triggers burn+compound cycle: collects LP fees, burns tokens, deepens liquidity, sends 5% upstream

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fire_reactor Rate-limited

fire_reactor 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": {
    "fire_reactor": {
      "limits": [
        {
          "counter": "fire_reactor_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 Baselings, so you can run agents against it safely.

FAQ

Questions about fire_reactor

What does the fire_reactor tool do? +

Fire a reactor (permissionless). Triggers burn+compound cycle: collects LP fees, burns tokens, deepens liquidity, sends 5% upstream. Any reactor can be fired every 2 hours. Costs ~$0.01 gas. After firing, MfT price dislocates across pools — arb opportunity. It is categorised as a Execute tool in the Baselings MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fire_reactor? +

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

What risk level is fire_reactor? +

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

Can I rate-limit fire_reactor? +

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

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

fire_reactor is provided by the Baselings MCP server (jimbo530/baselings-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.