run_calibrate

A execute tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/run-calibrate.md

WHAT IT DOES

What run_calibrate does on Kiln

AI agents invoke run_calibrate to trigger actions in Kiln. 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.

RISK

Why run_calibrate is rated High

The tool triggers execution of calibration procedures on 3D printers, which constitute external operations with effects dependent on printer state and configuration. While not destructive (calibration is reversible) or financial, it executes commands that affect physical device behavior.

From the tool's definition Tool name 'run_calibrate' and context of 3D printer control via OctoPrint, Moonraker, Bambu, Prusa, Elegoo platforms indicates execution of calibration routines on physical hardware.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_calibrate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_calibrate, this is the rule to start with:

run_calibrate Rate-limited

run_calibrate 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": {
    "run_calibrate": {
      "limits": [
        {
          "counter": "run_calibrate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every run_calibrate call is checked against it from then on.

FAQ

Questions about run_calibrate

What does the run_calibrate tool do? +

run_calibrate is a execute tool on the Kiln MCP server. It is categorised as a Execute tool in the Kiln MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_calibrate? +

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

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

Can I rate-limit run_calibrate? +

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

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

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

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 402 Kiln tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →