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 first) 3....

Part of the Name Whisper — ENS Intelligence Layer server.

manage_fuses can permanently delete data in Name Whisper — ENS Intelligence Layer, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

Free to start. No card required.

AI agents may call manage_fuses to permanently remove or destroy resources in Name Whisper — ENS Intelligence Layer. 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 manage_fuses in a loop, permanently destroying resources in Name Whisper — ENS Intelligence Layer. 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": [
    "manage_fuses"
  ]
}

See the full Name Whisper — ENS Intelligence Layer policy for all 42 tools.

Get this rule live on your own Name Whisper — ENS Intelligence Layer server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NAME WHISPER — ENS INTELLIGENCE LAYER →

View all 42 tools →

These attack patterns abuse exactly the kind of access manage_fuses 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 manage_fuses only ever does what you allow.

SECURE NAME WHISPER — ENS INTELLIGENCE LAYER →

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

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 — ENS Intelligence Layer 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? +

Register the Name Whisper — ENS Intelligence Layer MCP server in PolicyLayer and add a rule for manage_fuses: 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 Name Whisper — ENS Intelligence Layer. Nothing to install.

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

Set action: deny in the PolicyLayer 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 — ENS Intelligence Layer MCP server (https://namewhisper.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Name Whisper — ENS Intelligence Layer tool call.

Deterministic rules across all 42 Name Whisper — ENS Intelligence Layer 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.