List files stored on the Bambu Lab printer
AI agents call list_printer_files 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 or queries data about files on the printer with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because listing files poses minimal risk even if misused by an AI agent—it cannot cause damage, financial loss, or unintended operations.
From the tool's definition Tool name 'list_printer_files' and description 'List files stored on the Bambu Lab printer' indicate a query operation that retrieves information about files without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List files stored on the Bambu Lab printer. 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 list_printer_files: 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.
list_printer_files 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 list_printer_files 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 list_printer_files. 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.
list_printer_files 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 →