Merge vertices in an STL file closer than the specified tolerance
AI agents use merge_vertices to create or update resources in Bambu Printer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bambu Printer environment.
This tool creates reversible modifications to STL file data by consolidating nearby vertices. While it alters model geometry, the change is non-destructive and reversible (vertices can be re-separated or the original file restored). It does not delete data permanently, execute arbitrary code, or trigger external side effects beyond file manipulation.
From the tool's definition Tool description states it "Merge vertices in an STL file closer than the specified tolerance" — this modifies STL file geometry by consolidating vertices, altering the 3D model data structure.
Attacks that exploit this kind of access
Merge vertices in an STL file closer than the specified tolerance. It is categorised as a Write tool in the Bambu Printer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bambu Printer MCP server in PolicyLayer and add a rule for merge_vertices: 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 Bambu Printer. Nothing to install.
merge_vertices 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 merge_vertices 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 merge_vertices. 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.
merge_vertices is provided by the Bambu Printer MCP server (rowbotik/bambu-printer-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 →