arcane_registry_delete

// WHEN AI AGENTS USE THIS TOOL

AI agents may call arcane_registry_delete to permanently remove or destroy resources in Arcane. 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.

// WHY ENFORCE A POLICY ON ARCANE_REGISTRY_DELETE

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

// RECOMMENDED POLICY

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

arcane.yaml

tools:
  arcane_registry_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Arcane policy for all 180 tools.

// DETAILS

Tool Name arcane_registry_delete

Category Destructive

MCP Server Arcane MCP Server

Risk Level Critical

// MORE ARCANE TOOLS

Destructive arcane_apikey_delete Destructive arcane_container_delete Destructive arcane_environment_delete Destructive arcane_event_delete Destructive arcane_git_repo_delete Destructive arcane_gitops_delete Destructive arcane_image_delete Destructive arcane_image_prune

View all 180 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

arcane_registry_delete is one of the critical-risk operations in Arcane. 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.

// RELATED READING

// FAQ

What does the arcane_registry_delete tool do? +

Delete a container registry configuration. It is categorised as a Destructive tool in the Arcane 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 arcane_registry_delete? +

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

What risk level is arcane_registry_delete? +

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

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

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

arcane_registry_delete is provided by the Arcane MCP server (@randomsynergy/arcane-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.