print_to_printer · Formlabs Local MCP: Risk & Policy

WHAT IT DOES

What print_to_printer does on Formlabs Local

AI agents invoke print_to_printer to trigger actions in Formlabs Local. 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 print_to_printer needs a policy

The tool name strongly implies it triggers a physical print job on a Formlabs 3D printer. This is an external operation with real-world consequences (consuming resin/materials, occupying the printer, potentially running for hours). The description is empty, lowering confidence slightly, but the server context and sibling tools (auto_layout, auto_support, auto_pack) confirm this is part of a 3D printing workflow.

From the tool's definition Tool name 'print_to_printer' on a server that 'enabling users to drive Formlabs printers from chat prompts'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

print_to_printer Rate-limited

print_to_printer 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": {
    "print_to_printer": {
      "limits": [
        {
          "counter": "print_to_printer_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 Formlabs Local, so you can run agents against it safely.

FAQ

Questions about print_to_printer

What does the print_to_printer tool do? +

print_to_printer. It is categorised as a Execute tool in the Formlabs Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on print_to_printer? +

Register the Formlabs Local MCP server in PolicyLayer and add a rule for print_to_printer: 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 Formlabs Local. Nothing to install.

What risk level is print_to_printer? +

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

Can I rate-limit print_to_printer? +

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

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

print_to_printer is provided by the Formlabs Local MCP server (mkebiclioglu/formlabs-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.