Start printing a G-code file already on the Bambu Lab printer
AI agents invoke start_print_job to trigger actions in Bambu Printer. 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.
This is an Execute category tool because it triggers an external operation (3D printer activation) with effects that depend on the caller's input and cannot be trivially reversed mid-execution. While not Destructive (printing can be cancelled), it commands irreversible material consumption and physical state changes.
From the tool's definition The tool 'start_print_job' performs an external operation that triggers physical printer behavior: 'Start printing a G-code file already on the Bambu Lab printer'.
Attacks that exploit this kind of access
Start printing a G-code file already on the Bambu Lab printer. It is categorised as a Execute tool in the Bambu Printer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bambu Printer MCP server in PolicyLayer and add a rule for start_print_job: 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.
start_print_job 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 start_print_job 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 start_print_job. 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.
start_print_job 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 →