Skip specific objects during a multi-object print. Useful for excluding failed parts without stopping the entire print.
AI agents invoke skip_objects to trigger actions in Bambu Lab MCP Server. 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 actively intervenes in an ongoing physical 3D print job by commanding the printer to skip certain objects. It triggers an external hardware operation with real-world consequences — skipped objects cannot be retroactively printed in the same job. While not strictly 'destructive' in a data sense, it irreversibly alters the print outcome.
From the tool's definition 'Skip specific objects during a multi-object print' and 'excluding failed parts without stopping the entire print'
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access skip_objects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bambu Lab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for skip_objects:
{
"version": "1",
"default": "deny",
"tools": {
"skip_objects": {
"limits": [
{
"counter": "skip_objects_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}skip_objects stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Skip specific objects during a multi-object print. Useful for excluding failed parts without stopping the entire print. It is categorised as a Execute tool in the Bambu Lab MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bambu Lab MCP Server 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 Lab MCP Server. 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 Lab MCP Server MCP server (schwarztim/bambu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bambu Lab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Bambu Lab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.