Distribute multiple elements with even spacing along an axis. Sorts by the chosen axis, keeps the leading and trailing element fixed, and shifts everything in between so the gap between adjacent elements is constant. Needs ≥ 3 elements. All-or-nothing on missing ids.
AI agents use distribute_elements to create or update resources in Whiteboard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whiteboard environment.
This tool creates or modifies data (element positions) reversibly without executing arbitrary code, deleting data, or financial impact. The operation is a standard layout adjustment common in drawing applications and can be undone, fitting the Write category at low severity since blast radius is confined to diagram formatting.
From the tool's definition Tool modifies element positions on canvas by distributing spacing—"shifts everything in between so the gap between adjacent elements is constant"—creating a reversible layout change.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Distribute multiple elements with even spacing along an axis. Sorts by the chosen axis, keeps the leading and trailing element fixed, and shifts everything in between so the gap between adjacent elements is constant. Needs ≥ 3 elements. All-or-nothing on missing ids. It is categorised as a Write tool in the Whiteboard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whiteboard MCP server in PolicyLayer and add a rule for distribute_elements: 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 Whiteboard. Nothing to install.
distribute_elements 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 distribute_elements 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 distribute_elements. 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.
distribute_elements is provided by the Whiteboard MCP server (kamiazya/whiteboard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →