Enable or disable camera recording on the printer
AI agents use camera_record to create or update resources in Bambu Lab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bambu Lab MCP Server environment.
This tool modifies the camera recording state (on/off) on the printer, which is a reversible configuration change. It does not execute code, delete data, or involve financial transactions. Misuse could enable unwanted surveillance or disable monitoring during a print job, but the effects are reversible.
From the tool's definition Enable or disable camera recording on the printer
Documented attack patterns abuse exactly the kind of access camera_record 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 camera_record:
{
"version": "1",
"default": "deny",
"tools": {
"camera_record": {
"limits": [
{
"counter": "camera_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} camera_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enable or disable camera recording on the printer. It is categorised as a Write tool in the Bambu Lab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bambu Lab MCP Server MCP server in PolicyLayer and add a rule for camera_record: 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.
camera_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the camera_record 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 camera_record. 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.
camera_record 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.