archimate_delete_element

THE RISK

Critical Risk

Why archimate_delete_element needs a policy

This tool permanently removes architecture model elements and their relationships from the ArchiMate repository. Deletion of model elements in an architecture design system is irreversible and could corrupt dependent designs, break model consistency, or lose critical architectural documentation.

From the tool's definition Tool name 'archimate_delete_element' combined with description 'Delete an element and its associated relationships' explicitly indicates irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access archimate_delete_element gives an agent:

POLICY

How to control archimate_delete_element

PolicyLayer is an MCP gateway — it sits between your AI agents and ArchiMate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for archimate_delete_element:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "archimate_delete_element"
  ]
}

archimate_delete_element disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register ArchiMate MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ArchiMate MCP Server tools

Destructive archimate_delete_relationship Delete a relationship Write archimate_add_connection_to_view Manually add a connection (line/arrow) between two diagram objects in a view. Normally unn Write archimate_add_to_view Add an element to a diagram view. Connections for relationships between this element and a Write archimate_configure_audit Configure audit logging for model operations Write archimate_create_application_element Create an Application layer element (Chapter 9). Use for application components, services, Write archimate_create_business_element Create a Business layer element (Chapter 8). Use for actors, processes, services, and busi Write archimate_create_composite_element Create a composite element (Chapter 4). Use for grouping and locations. Write archimate_create_implementation_element Create an Implementation & Migration layer element (Chapter 12). Use for work packages, de

All 33 ArchiMate MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in ArchiMate MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about archimate_delete_element

What does the archimate_delete_element tool do? +

Delete an element and its associated relationships. It is categorised as a Destructive tool in the ArchiMate 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 archimate_delete_element? +

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

What risk level is archimate_delete_element? +

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

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

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

archimate_delete_element is provided by the ArchiMate MCP Server MCP server (thijs-hakkenberg/archimate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ArchiMate MCP Server tool call.

Start from ArchiMate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →