Get the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, resolved slicer profile paths, match confidence, and recommended load_filaments when the printer model is known.
AI agents call get_printer_filaments to retrieve information from Bambu Printer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries current filament inventory status from the printer. It performs read-only operations: fetching AMS slot status, resolving slicer profiles, and providing recommendations. No data is created, modified, deleted, or execution is triggered. The tool has no destructive or irreversible effects. Misuse by an AI agent would only expose existing printer state information, posing minimal risk.
From the tool's definition Tool name 'get_printer_filaments' and description 'Get the live AMS/external filament inventory from the printer' indicate retrieval of printer state data with no modification capability. The phrase 'Get' and 'inventory' describe a query operation.
Attacks that exploit this kind of access
Get the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, resolved slicer profile paths, match confidence, and recommended load_filaments when the printer model is known. It is categorised as a Read tool in the Bambu Printer MCP Server, which means it retrieves data without modifying state.
Register the Bambu Printer MCP server in PolicyLayer and add a rule for get_printer_filaments: 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.
get_printer_filaments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_printer_filaments 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 get_printer_filaments. 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.
get_printer_filaments 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 →