Automatically arrange nodes using a layered graph layout algorithm.
AI agents use auto_layout to create or update resources in Flowchart MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flowchart MCP environment.
auto_layout modifies flowchart node positions but does not create, delete, or destroy data—the nodes and edges themselves remain intact. This is a reversible layout operation (the diagram can be re-arranged), placing it in Write rather than Execute or Destructive. Severity is low because misuse simply produces a poor layout, with no data loss, financial impact, or system-level consequences.
From the tool's definition Tool modifies the spatial arrangement of flowchart nodes through an automatic layout algorithm, which changes the diagram's visual state reversibly. Description explicitly states 'automatically arrange nodes', indicating data modification.
Attacks that exploit this kind of access
Automatically arrange nodes using a layered graph layout algorithm. It is categorised as a Write tool in the Flowchart MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flowchart MCP server in PolicyLayer and add a rule for 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 Flowchart MCP. Nothing to install.
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 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 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.
auto_layout is provided by the Flowchart MCP server (zafer-liu/flowchart_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
auto_layout is one line of Flowchart's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →