AI agents use archimate_update_element to create or update resources in ArchiMate MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ArchiMate MCP Server environment.
This tool modifies existing architectural elements reversibly—changes can be undone or corrected by subsequent updates. It is not destructive (no permanent deletion), not Execute (no code execution or shell commands), and not Financial.
From the tool's definition Tool name 'archimate_update_element' and description 'Update an existing element' indicate modification of existing data within ArchiMate models. The server description confirms it 'modify[s]...ArchiMate architecture models'.
Documented attack patterns abuse exactly the kind of access archimate_update_element gives an agent:
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_update_element:
{
"version": "1",
"default": "deny",
"tools": {
"archimate_update_element": {
"limits": [
{
"counter": "archimate_update_element_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} archimate_update_element stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing element. It is categorised as a Write tool in the ArchiMate MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ArchiMate MCP Server MCP server in PolicyLayer and add a rule for archimate_update_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.
archimate_update_element is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the archimate_update_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.
Set action: deny in the PolicyLayer policy for archimate_update_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.
archimate_update_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.
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.
Free to start. No card required.
33 ArchiMate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.