Apply automatic layout to a process for better visual positioning
AI agents use bpmn_auto_layout to create or update resources in MCP-BPMN Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-BPMN Server environment.
The tool modifies BPMN diagram layout/positioning, which is a reversible change to diagram metadata. This is a Write operation rather than Read (it changes state), Execute (no code execution), or Destructive (changes are non-permanent and can be adjusted).
From the tool's definition Tool name 'bpmn_auto_layout' and description 'Apply automatic layout to a process for better visual positioning' indicate modification of an existing BPMN diagram's visual properties without destructive or executable side effects.
Documented attack patterns abuse exactly the kind of access bpmn_auto_layout gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-BPMN Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bpmn_auto_layout:
{
"version": "1",
"default": "deny",
"tools": {
"bpmn_auto_layout": {
"limits": [
{
"counter": "bpmn_auto_layout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bpmn_auto_layout 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.
Apply automatic layout to a process for better visual positioning. It is categorised as a Write tool in the MCP-BPMN Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-BPMN Server MCP server in PolicyLayer and add a rule for bpmn_auto_layout: 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 MCP-BPMN Server. Nothing to install.
bpmn_auto_layout 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 bpmn_auto_layout 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 bpmn_auto_layout. 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.
bpmn_auto_layout is provided by the MCP-BPMN Server MCP server (oisee/mcp-bpmn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-BPMN 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.
41 MCP-BPMN Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.