Arrange models on the build platform. SLA printers only (Form 4, Form 3, etc.).
AI agents invoke auto_layout to trigger actions in Formlabs Local. 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.
The tool executes an automated operation on external hardware (Formlabs 3D printer) that arranges physical objects on a build platform. This is Execute rather than Write because it triggers a real-world physical operation with effects that depend on the arguments provided and cannot be trivially undone without manual intervention.
From the tool's definition 'Arrange models on the build platform' - this triggers automatic layout operations on physical hardware (SLA printers), which is a side-effect-bearing operation whose outcome depends on model arguments and printer state.
Attacks that exploit this kind of access
Arrange models on the build platform. SLA printers only (Form 4, Form 3, etc.). It is categorised as a Execute tool in the Formlabs Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Formlabs Local 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 Formlabs Local. Nothing to install.
auto_layout 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 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 Formlabs Local MCP server (mkebiclioglu/formlabs-local-mcp). 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 →