Add an element to a diagram view. Connections for relationships between this element and any element already in the view are drawn automatically - you do not need to call archimate_add_connection_to_view for them. The response lists every connection that was auto-drawn in autoConnectedRelationships.
AI agents use archimate_add_to_view 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.
The tool creates or modifies diagram views by adding elements and auto-drawing connections. This is a reversible data modification (elements and connections can be removed), so it falls under Write rather than Execute or Destructive. The blast radius is medium because incorrect additions could clutter or misrepresent architecture models, but changes are not permanent and can be undone.
From the tool's definition Tool adds elements to diagram views and automatically draws connections. The description explicitly states it modifies view contents ("Add an element to a diagram view") and creates relationships ("Connections for relationships between this element and any…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access archimate_add_to_view 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_add_to_view:
{
"version": "1",
"default": "deny",
"tools": {
"archimate_add_to_view": {
"limits": [
{
"counter": "archimate_add_to_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archimate_add_to_view 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.
Add an element to a diagram view. Connections for relationships between this element and any element already in the view are drawn automatically - you do not need to call archimate_add_connection_to_view for them. The response lists every connection that was auto-drawn in autoConnectedRelationships. 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_add_to_view: 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_add_to_view 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_add_to_view 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_add_to_view. 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_add_to_view 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.