reread_ams_rfid · Bambu Printer MCP: Risk & Policy

WHAT IT DOES

What reread_ams_rfid does on Bambu Printer

AI agents invoke reread_ams_rfid 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.

WHY IT NEEDS A POLICY

Why reread_ams_rfid needs a policy

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). While not destructive or financial, it triggers external hardware operations whose effects depend on printer state and the specific AMS slot targeted.

From the tool's definition Tool description states "Trigger a Bambu AMS RFID re-read" and "can move AMS filament." The word "Trigger" indicates initiating an external physical operation on printer hardware. Moving AMS filament is a mechanical action with real-world effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reread_ams_rfid Rate-limited

reread_ams_rfid stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reread_ams_rfid": {
      "limits": [
        {
          "counter": "reread_ams_rfid_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bambu Printer, so you can run agents against it safely.

FAQ

Questions about reread_ams_rfid

What does the reread_ams_rfid tool do? +

Trigger a Bambu AMS RFID re-read for one AMS slot. This can move AMS filament; use only when the printer is idle and unloaded. 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.

How do I enforce a policy on reread_ams_rfid? +

Register the Bambu Printer MCP server in PolicyLayer and add a rule for reread_ams_rfid: 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.

What risk level is reread_ams_rfid? +

reread_ams_rfid is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reread_ams_rfid? +

Yes. Add a rate_limit block to the reread_ams_rfid 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.

How do I block reread_ams_rfid completely? +

Set action: deny in the PolicyLayer policy for reread_ams_rfid. 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.

What MCP server provides reread_ams_rfid? +

reread_ams_rfid 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.