Generate support structures.
AI agents use auto_support to create or update resources in Formlabs Local — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Formlabs Local environment.
This tool generates (creates) support structures for a 3D print scene. It writes new data (support geometry) to the model/scene. It does not delete or irreversibly overwrite existing data, execute arbitrary code, or involve financial transactions. Misuse could result in incorrect support generation that wastes material or causes print failures, but the action is reversible (supports can be regenerated or removed).
From the tool's definition "Generate support structures" — creates new support structure data within a scene/model
Attacks that exploit this kind of access
Generate support structures. It is categorised as a Write tool in the Formlabs Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Formlabs Local MCP server in PolicyLayer and add a rule for auto_support: 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_support 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_support 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_support. 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_support 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 →