Copy a 3MF, JSON, or config file into the local template registry and register it under a template name.
AI agents use save_template 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 the local template registry by adding new templates, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. While it could affect future 3D print jobs if a malicious template is saved, the direct action is file creation/registration.
From the tool's definition Tool description states 'Copy a 3MF, JSON, or config file into the local template registry and register it under a template name.' The actions of copying files and registering them are write operations that create new entries in a template registry.
Attacks that exploit this kind of access
Copy a 3MF, JSON, or config file into the local template registry and register it under a template name. 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 save_template: 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.
save_template 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 save_template 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 save_template. 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.
save_template 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 →