prepare-burn-hat

Prepare a transaction to burn (remove) a hat from a wearer

SERVERHats Protocol MCP Server SOURCEdennisonbertram/mcp-hats

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dennisonbertram-mcp-hats/prepare-burn-hat.md

WHAT IT DOES

What prepare-burn-hat does on Hats Protocol MCP Server

AI agents call prepare-burn-hat to permanently remove resources in Hats Protocol MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why prepare-burn-hat is rated Critical

Burning a hat removes a role/permission from a wearer on a blockchain. Blockchain transactions are irreversible by nature — once committed, the hat is permanently burned from that address. This is a destructive, irreversible action affecting decentralized organizational roles and permissions.

From the tool's definition prepare a transaction to burn (remove) a hat from a wearer

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare-burn-hat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hats Protocol MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare-burn-hat, this is the rule to start with:

prepare-burn-hat Hidden

prepare-burn-hat is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "prepare-burn-hat"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hats Protocol MCP Server, apply this rule, and every prepare-burn-hat call is checked against it from then on.

FAQ

Questions about prepare-burn-hat

What does the prepare-burn-hat tool do? +

Prepare a transaction to burn (remove) a hat from a wearer. It is categorised as a Destructive tool in the Hats Protocol MCP Server 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 prepare-burn-hat? +

Register the Hats Protocol MCP Server MCP server in PolicyLayer and add a rule for prepare-burn-hat: 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 Hats Protocol MCP Server. Nothing to install.

What risk level is prepare-burn-hat? +

prepare-burn-hat 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 prepare-burn-hat? +

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

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

prepare-burn-hat is provided by the Hats Protocol MCP Server MCP server (dennisonbertram/mcp-hats). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hats Protocol MCP Server, and thousands of servers like it.

This server

All 11 Hats Protocol MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →