Set the nozzle diameter (for printing profile selection)
AI agents use set_nozzle to create or update resources in Bambu Lab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bambu Lab MCP Server environment.
This tool writes/modifies printer hardware configuration (nozzle diameter setting). While the change is reversible and doesn't delete data or move money, it alters the printer's operational parameters, affecting future print quality and behavior.
From the tool's definition The tool 'set_nozzle' modifies the nozzle diameter setting on the 3D printer hardware, which is a configuration change that affects subsequent print jobs.
Documented attack patterns abuse exactly the kind of access set_nozzle 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 set_nozzle:
{
"version": "1",
"default": "deny",
"tools": {
"set_nozzle": {
"limits": [
{
"counter": "set_nozzle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_nozzle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the nozzle diameter (for printing profile selection). It is categorised as a Write tool in the Bambu Lab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bambu Lab MCP Server MCP server in PolicyLayer and add a rule for set_nozzle: 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.
set_nozzle 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 set_nozzle 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 set_nozzle. 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.
set_nozzle 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.