Translate the model so its geometric center is at the origin (0,0,0)
AI agents use center_model 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 modifies 3D model geometry by translating its coordinates. This is a Write operation because it creates a modified version of the model data that can be undone or reverted. The severity is medium because misuse could corrupt or render a model unsuitable for printing, but the effect is reversible (re-centering or reloading the original file restores it).
From the tool's definition 'Translate the model so its geometric center is at the origin' describes modifying a model's spatial properties, which is a reversible transformation of file data.
Attacks that exploit this kind of access
Translate the model so its geometric center is at the origin (0,0,0). 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 center_model: 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.
center_model 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 center_model 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 center_model. 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.
center_model 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 →