Skip specific object IDs during a running multi-object print using the printer
AI agents invoke skip_objects 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 tool modifies the behavior of an active print job by skipping objects mid-print. It triggers an external operation on physical hardware (the printer), and the skipped objects cannot be re-printed in the current job without restarting — making it effectively irreversible for those objects.
From the tool's definition 'Skip specific object IDs during a running multi-object print using the printer'
Attacks that exploit this kind of access
Skip specific object IDs during a running multi-object print using the 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 skip_objects: 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.
skip_objects 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 skip_objects 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 skip_objects. 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.
skip_objects 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 →