// SCAN REPORT

Bambu Printer

37 tools. 28 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

28 can modify or destroy data

9 read-only

37 tools total

Community server · catalogue entry verified 02/07/2026

How to control Bambu Printer ↓

TOOL MAP

What Bambu Printer exposes to your agents

Read (9) Write / Execute (26) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Bambu Printer tools

Destructive · High cancel_print Cancelling a print job is irreversible — the in-progress print is destroyed, any partially printed object is ruined, and the job cannot be resumed. Destructive · High delete_printer_file The tool permanently removes files from the printer's storage without the ability to undo or recover them. Execute · Medium clear_hms_errors This tool triggers an external operation on a physical device (Bambu Lab printer) via MQTT command to clear error states. Execute · High reread_ams_rfid This tool executes a command that causes a physical device (the AMS—Automated Material System) to perform an action (RFID re-read and potential filament movement).

28 of Bambu Printer's 37 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Bambu Printer

PolicyLayer is an MCP gateway — it sits between your AI agents and Bambu Printer, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "cancel_print": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "center_model": {
    "limits": [
      {
        "counter": "center_model_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "camera_snapshot": {
    "limits": [
      {
        "counter": "camera_snapshot_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Bambu Printer — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BAMBU PRINTER →

Instant setup, no code required.

FULL CATALOGUE

All 37 Bambu Printer tools

DESTRUCTIVE 2 tools

Destructive cancel_print Cancel the current print job on the Bambu Lab printer Destructive delete_printer_file Delete a file from the Bambu Lab printer

EXECUTE 14 tools

Execute blender_mcp_edit_model Send STL-edit instructions to a Blender MCP bridge command for advanced model edits Execute clear_hms_errors Clear HMS or print error state on the Bambu Lab printer using the clean_print_error MQTT command. Execute pause_print Pause the current print job on the Bambu Lab printer (resumable via resume_print) Execute print_3mf Print a 3MF file on a Bambu Lab printer. Auto-slices if the 3MF has no gcode. IMPORTANT: bambu_model must be s Execute print_collar_charm Print a prepared two-part dog collar charm project using the fixed tray policy: inner/smaller object -> black Execute reread_ams_rfid Trigger a Bambu AMS RFID re-read for one AMS slot. This can move AMS filament; use only when the printer is id Execute resume_print Resume a paused print job on the Bambu Lab printer Execute set_airduct_mode Set H2/P2 airduct mode to cooling or heating. Execute set_ams_drying Start or stop the AMS filament drying cycle. Available on AMS units with heating capability (AMS Pro / AMS-HT) Execute set_fan_speed Set a Bambu printer fan speed percentage using the printer Execute skip_objects Skip specific object IDs during a running multi-object print using the printer Execute slice_stl Slice an STL or 3MF file using a slicer to generate printable G-code or sliced 3MF. IMPORTANT: bambu_model mus Execute slice_with_template Slice an STL or 3MF using a named template from the local registry. This is a higher-level wrapper around slic Execute start_print_job Start printing a G-code file already on the Bambu Lab printer

WRITE 12 tools

Write center_model Translate the model so its geometric center is at the origin (0,0,0) Write extend_stl_base Extend the base of an STL file by a specified amount Write lay_flat Rotate the model so its largest flat face lies on the XY plane (Z=0) Write merge_vertices Merge vertices in an STL file closer than the specified tolerance Write rotate_stl Rotate an STL file by specified angles (degrees) Write save_template Copy a 3MF, JSON, or config file into the local template registry and register it under a template name. Write scale_stl Scale an STL file by specified factors Write set_light Set a Bambu printer light node mode using the printer Write set_print_speed Set the active print speed mode: silent, standard, sport, or ludicrous. Write set_temperature Set the temperature of a printer component (bed, nozzle) Write upload_file Upload a local file to the Bambu Lab printer Write upload_gcode Upload a G-code file to the Bambu Lab printer

READ 9 tools

Read camera_snapshot Capture a single JPEG frame from the printer Read get_printer_filaments Get the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, Read get_printer_status Get the current status of the Bambu Lab printer Read get_slice_settings Inspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything. Read get_stl_info Get detailed information about an STL file (bounding box, face count, dimensions) Read list_3mf_plate_objects List object IDs from a sliced 3MF plate. Use these IDs with skip_objects during a running print. Read list_printer_files List files stored on the Bambu Lab printer Read list_templates List saved slicing templates from the local template registry directory. Read resolve_3mf_ams_slots Inspect a sliced 3MF and match its tray_info_idx filament requirements against the live AMS inventory. Does no

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Bambu Printer

Can an AI agent delete data through the Bambu Printer MCP server? +

Yes. The Bambu Printer server exposes 2 destructive tools including cancel_print, delete_printer_file. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Bambu Printer? +

The Bambu Printer server has 12 write tools including center_model, extend_stl_base, lay_flat. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Bambu Printer.

How many tools does the Bambu Printer MCP server expose? +

37 tools across 4 categories: Destructive, Execute, Read, Write. 9 are read-only. 28 can modify, create, or delete data.

How do I enforce a policy on Bambu Printer? +

Register the Bambu Printer MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Bambu Printer tool call.

Deterministic rules across all 37 Bambu Printer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BAMBU PRINTER →

Instant setup, no code required.

37 Bambu Printer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.