Control the canvas viewport. Use scrollToContent to zoom-to-fit,
AI agents invoke set_viewport 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.
This tool manipulates the viewport state of a live tldraw canvas — scrolling and zooming — which constitutes triggering an external operation (UI state change) rather than simply reading data or writing persistent content. It falls under Execute as it controls the live canvas environment. Misuse has moderate blast radius since it affects the view but not the underlying data.
From the tool's definition 'Control the canvas viewport' and 'zoom-to-fit' indicate triggering external operations on a live canvas
Attacks that exploit this kind of access
Control the canvas viewport. Use scrollToContent to zoom-to-fit,. 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.
Register the tldraw MCP Server MCP server in PolicyLayer and add a rule for set_viewport: 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.
set_viewport is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_viewport 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 set_viewport. 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.
set_viewport 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.
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 →