Manage Bambu Labs 3D Printers thru your Agent

• Outcome: Review
• Latest audit: Sep 10, 2026 · 4:39 AM UTC
• Version: 1.0.0

Overview

This skill is a disclosed Bambu printer control helper, but it exposes an under-scoped validation bypass for raw G-code sent to physical hardware.

Review this skill before installing if you use agent-driven printer control. Its ordinary monitoring, print, file, camera, config, and calibration guidance is coherent, but do not let an agent use `gcode send --no-check` unless you explicitly understand and accept the hardware risk; prefer validated G-code commands and keep access codes in files or stdin rather than command-line flags.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Tool Misuse: Tool Parameter Abuse, Chaining Abuse, Unsafe Defaults
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Tool Parameter Abuse

High

• Category: Tool Misuse

Content

- Use `light on|off|status`.

### Gcode and calibration
- Use `gcode send <line...>` or `gcode send --stdin` (confirmation required; `--no-check` skips validation).
- Avoid combining `--access-code-stdin` with `gcode send --stdin`; use an access code file instead.
- Use `calibrate` with `--no-bed-level`, `--no-motor-noise`, `--no-vibration` when requested.

• Confidence: 92% confidence
• Finding: The skill explicitly documents use of `gcode send` with the `--no-check` flag, which disables validation for arbitrary G-code sent to a physical printer. In this context, that creates a real tool-parameter abuse risk because an agent could be guided to bypass safety checks and issue unsafe motion, heating, or control commands that can damage hardware or create safety hazards.

Tool Parameter Abuse

High

• Category: Tool Misuse

Content

- `files download <remote> --out <path|->` (use `--force` for stdout on TTY)
- `files delete <remote>` - confirmation required.
- `camera snapshot [--out <path|->]` - default `snapshot.jpg` (use `--force` for stdout on TTY).
- `gcode send <line...> | --stdin` - confirmation required; `--no-check` to skip validation.
- `ams status` - show AMS data.
- `calibrate [--no-bed-level] [--no-motor-noise] [--no-vibration]` - confirmation required.
- `home` - home axes.

• Confidence: 94% confidence
• Finding: The reference explicitly documents a `--no-check` option for `gcode send` that disables validation on direct G-code sent to a physical printer. In a skill whose purpose is to translate user requests into safe printer-control commands, exposing a bypass for safety checks materially increases the chance that an agent or user could issue unsafe motion/heating commands that damage hardware or create safety hazards.

Static analysis

No suspicious patterns detected.