Download a model from MakerWorld and print it on the connected printer.
AI agents invoke makerworld_print to trigger actions in Bambu Lab MCP Server. 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.
This tool performs multiple actions: fetching a remote model from an external source (MakerWorld) and then commanding the 3D printer to execute a print job. Printing involves physical hardware operation (motors, heaters, filament extrusion) that cannot easily be undone mid-job, consumes materials, and could cause damage if misused.
From the tool's definition 'Download a model from MakerWorld and print it on the connected printer' — triggers an external download and initiates a physical print job on hardware
Documented attack patterns abuse exactly the kind of access makerworld_print 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 makerworld_print:
{
"version": "1",
"default": "deny",
"tools": {
"makerworld_print": {
"limits": [
{
"counter": "makerworld_print_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} makerworld_print 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.
Free to start. No card required.
Download a model from MakerWorld and print it on the connected printer. It is categorised as a Execute tool in the Bambu Lab MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bambu Lab MCP Server MCP server in PolicyLayer and add a rule for makerworld_print: 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.
makerworld_print is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the makerworld_print 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 makerworld_print. 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.
makerworld_print 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.