Request a full status push from the printer and return it. Includes temperatures, print progress, AMS state, fan speeds, and more. Note: pushall should not be called more than once every 5 minutes on P1P.
AI agents call printer_get_status to retrieve information from Bambu Lab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves real-time monitoring data from the printer without modifying any state or triggering operations. It is a passive query operation that gathers sensor readings and device status. The only constraint mentioned is a rate limit (not more than once every 5 minutes on P1P), which is a safeguard against resource exhaustion, not evidence of side effects.
From the tool's definition Tool name is 'printer_get_status' and description states it 'Request[s] a full status push from the printer and return[s] it.' The action is purely retrievable—querying temperatures, print progress, AMS state, and fan speeds with no modifications, deletions,…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access printer_get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bambu Lab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for printer_get_status:
{
"version": "1",
"default": "deny",
"tools": {
"printer_get_status": {}
}
}printer_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Request a full status push from the printer and return it. Includes temperatures, print progress, AMS state, fan speeds, and more. Note: pushall should not be called more than once every 5 minutes on P1P. It is categorised as a Read tool in the Bambu Lab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bambu Lab MCP Server MCP server in PolicyLayer and add a rule for printer_get_status: 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 Lab MCP Server. Nothing to install.
printer_get_status 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 printer_get_status 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 printer_get_status. 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.
printer_get_status is provided by the Bambu Lab MCP Server MCP server (schwarztim/bambu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bambu Lab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Bambu Lab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.