auto_layout · tldraw MCP Server MCP: Risk & Policy

WHAT IT DOES

What auto_layout does on tldraw MCP Server

AI agents invoke auto_layout to trigger actions in tldraw MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why auto_layout needs a policy

This tool triggers an algorithmic operation that repositions/rearranges existing canvas elements. It executes a layout algorithm that modifies the state of the canvas (element positions), making it a Write/Execute operation. Since it runs an algorithm that transforms the canvas state rather than simply creating or updating a single known field, Execute is the most appropriate category.

From the tool's definition Automatically arrange elements using a layout algorithm

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_layout Rate-limited

auto_layout stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auto_layout": {
      "limits": [
        {
          "counter": "auto_layout_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches tldraw MCP Server, so you can run agents against it safely.

FAQ

Questions about auto_layout

What does the auto_layout tool do? +

Automatically arrange elements using a layout algorithm. It is categorised as a Execute tool in the tldraw MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auto_layout? +

Register the tldraw MCP Server 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 tldraw MCP Server. Nothing to install.

What risk level is auto_layout? +

auto_layout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit auto_layout? +

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.

How do I block auto_layout completely? +

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.

What MCP server provides auto_layout? +

auto_layout is provided by the tldraw MCP Server MCP server (mihai-codes/tldraw-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

auto_layout is one line of tldraw MCP Server'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 →