save_print_checkpoint · Kiln MCP: Risk & Policy

WHAT IT DOES

What save_print_checkpoint does on Kiln

AI agents use save_print_checkpoint to create or update resources in Kiln — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.

WHY IT NEEDS A POLICY

Why save_print_checkpoint needs a policy

This tool creates or modifies checkpoint data during 3D printing operations, enabling recovery from interruptions. While reversible (checkpoints can be overwritten or deleted), it modifies persistent printer state. Severity is medium because misuse could corrupt print jobs or waste material/time, but lacks the irreversibility of Destructive actions or financial impact.

From the tool's definition Tool name 'save_print_checkpoint' and context of 3D printer control (OctoPrint, Moonraker, Bambu, Prusa, Elegoo) indicate creation or modification of checkpoint data. The 'save' verb suggests writing/persisting state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_print_checkpoint Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_print_checkpoint": {
      "limits": [
        {
          "counter": "save_print_checkpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kiln, so you can run agents against it safely.

FAQ

Questions about save_print_checkpoint

What does the save_print_checkpoint tool do? +

save_print_checkpoint. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_print_checkpoint? +

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

What risk level is save_print_checkpoint? +

save_print_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_print_checkpoint? +

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

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

save_print_checkpoint is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.