Set H2/P2 airduct mode to cooling or heating.
AI agents invoke set_airduct_mode 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 triggers an external operation on a physical 3D printer by changing its airduct mode. It controls hardware state (cooling vs heating), which is an action with real-world effects on the printer's operation. It fits Execute as it triggers an external physical operation; misuse could damage prints or hardware components.
From the tool's definition Set H2/P2 airduct mode to cooling or heating
Attacks that exploit this kind of access
Set H2/P2 airduct mode to cooling or heating. 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 set_airduct_mode: 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.
set_airduct_mode 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 set_airduct_mode 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_airduct_mode. 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_airduct_mode 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 →