slice_with_template · Bambu Printer MCP: Risk & Policy

WHAT IT DOES

What slice_with_template does on Bambu Printer

AI agents invoke slice_with_template 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 slice_with_template needs a policy

Slicing is an external execution operation that processes input files and produces output artifacts. It triggers a computational pipeline (the slicer engine) and writes output files, making it Execute-level. Misuse could generate incorrect gcode files that could be sent to a printer, potentially causing print failures or hardware issues, justifying high severity.

From the tool's definition 'Slice an STL or 3MF using a named template' — triggers an external slicing operation (compute-intensive process that generates gcode/output files) as a wrapper around slice_stl

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

slice_with_template Rate-limited

slice_with_template 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": {
    "slice_with_template": {
      "limits": [
        {
          "counter": "slice_with_template_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 slice_with_template

What does the slice_with_template tool do? +

Slice an STL or 3MF using a named template from the local registry. This is a higher-level wrapper around slice_stl for template-based workflows. 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 slice_with_template? +

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

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

Can I rate-limit slice_with_template? +

Yes. Add a rate_limit block to the slice_with_template 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 slice_with_template completely? +

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

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