Critical Risk →

burn_key

Burn ONE key on a round to permanently boost your share on the remaining keys. WHAT IT DOES: invokes the Anchor program's burn_key_token instruction. The burnt key's stake is folded into the round's divPerKeyScaled, increasing the per-key dividend rate for every remaining keyholder. Your remainin...

Risk signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets

Part of the Fomox402 server.

burn_key can permanently delete data in Fomox402, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FOMOX402 →

Free to start. No card required.

AI agents may call burn_key to permanently remove or destroy resources in Fomox402. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call burn_key in a loop, permanently destroying resources in Fomox402. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "burn_key"
  ]
}

See the full Fomox402 policy for all 25 tools.

Get this rule live on your own Fomox402 server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FOMOX402 →

View all 25 tools →

These attack patterns abuse exactly the kind of access burn_key gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so burn_key only ever does what you allow.

SECURE FOMOX402 →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the burn_key tool do? +

Burn ONE key on a round to permanently boost your share on the remaining keys. WHAT IT DOES: invokes the Anchor program's burn_key_token instruction. The burnt key's stake is folded into the round's divPerKeyScaled, increasing the per-key dividend rate for every remaining keyholder. Your remaining keys benefit proportionally to your share of post-burn keys. WHEN TO USE: only when you hold many keys (>5) on a round whose pot is still ratcheting up. The math: if your_keys / total_keys is large, burning ONE key transfers a big chunk of your-vs-other dividend power — but you keep the rest of your keys. if your_keys / total_keys is small, the burn mostly subsidises others. IRREVERSIBLE: burnt keys are gone. The on-chain account is closed and the rent is reclaimed; you cannot re-mint a key without placing a new bid. RETURNS: { tx (Solana sig), gameId, keysBefore, keysAfter (= keysBefore - 1), newDivPerKeyScaled (the boosted rate) }. FAILURE MODES: burn_key_failed (no_keys) — you don't hold any keys on this round burn_key_failed (round_settled) — round is already gameOver ADVANCED USE — counter-burn defence: if a competitor is dominating divs by holding many keys, burning your own can flip the per-key rate higher than their additional bid cost, pricing them out. RELATED: claim_dividend (collect what your keys earned), place_bid (mints a fresh key — opposite of this).. It is categorised as a Destructive tool in the Fomox402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on burn_key? +

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

What risk level is burn_key? +

burn_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit burn_key? +

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

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

burn_key is provided by the Fomox402 MCP server (https://bot.staccpad.fun/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fomox402 tool call.

Deterministic rules across all 25 Fomox402 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.