Critical Risk →

manage_fuses

Manage fuses on a wrapped ENS name. Fuses are permission bits that can be permanently burned to restrict what can be done with a name. Three modes: 1. **read** — Check which fuses are currently burned on a name 2. **burn_owner_fuses** — Burn fuses on a name you own (CANNOT_UNWRAP must be burned ...

Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

namewhisper/ens-tools Destructive Risk 4/5

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

Without a policy, an AI agent could call manage_fuses in a loop, permanently destroying resources in Name Whisper. There is no undo for destructive operations. Intercept 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.

namewhisper-ens-tools.yaml
tools:
  manage_fuses:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Name Whisper policy for all 34 tools.

Tool Name manage_fuses
Category Destructive
Risk Level Critical

View all 34 tools →

Agents calling destructive-class tools like manage_fuses have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

manage_fuses is one of the critical-risk operations in Name Whisper. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the manage_fuses tool do? +

Manage fuses on a wrapped ENS name. Fuses are permission bits that can be permanently burned to restrict what can be done with a name. Three modes: 1. **read** — Check which fuses are currently burned on a name 2. **burn_owner_fuses** — Burn fuses on a name you own (CANNOT_UNWRAP must be burned first) 3. **burn_child_fuses** — As a parent, burn fuses on a subname (e.g. burn PARENT_CANNOT_CONTROL on sub.parent.eth) Owner-controlled fuses: - CANNOT_UNWRAP — prevents unwrapping (MUST be burned first before any other fuse) - CANNOT_BURN_FUSES — prevents burning additional fuses - CANNOT_TRANSFER — prevents transfers - CANNOT_SET_RESOLVER — prevents resolver changes - CANNOT_SET_TTL — prevents TTL changes - CANNOT_CREATE_SUBDOMAIN — prevents creating new subnames - CANNOT_APPROVE — prevents approving operators Parent-controlled fuses (for subnames): - PARENT_CANNOT_CONTROL — parent permanently gives up control over the subname - CAN_EXTEND_EXPIRY — allows the subname owner to extend their own expiry WARNING: All fuse burning is IRREVERSIBLE. Fuses expire when the name expires.. It is categorised as a Destructive tool in the Name Whisper 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 manage_fuses? +

Add a rule in your Intercept YAML policy under the tools section for manage_fuses. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.

What risk level is manage_fuses? +

manage_fuses 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 manage_fuses? +

Yes. Add a rate_limit block to the manage_fuses rule in your Intercept 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 manage_fuses completely? +

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

manage_fuses is provided by the Name Whisper MCP server (namewhisper/ens-tools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Name Whisper

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.