trigger_bed_level · Kiln MCP: Risk & Policy

WHAT IT DOES

What trigger_bed_level does on Kiln

AI agents invoke trigger_bed_level 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.

WHY IT NEEDS A POLICY

Why trigger_bed_level needs a policy

This tool triggers an external operation (bed leveling probe) on 3D printer hardware. While not destructive or financial, it is an Execute-category action because it causes the printer to perform an active mechanical procedure. Misuse could damage the printer (probe crash, improper calibration leading to nozzle collision) or waste materials.

From the tool's definition Tool name 'trigger_bed_level' and description 'Trigger a bed leveling / mesh probe on the printer' indicate the tool executes a physical operation on hardware (bed leveling/mesh probe) whose outcome depends on printer state and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_bed_level Rate-limited

trigger_bed_level 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": {
    "trigger_bed_level": {
      "limits": [
        {
          "counter": "trigger_bed_level_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 Kiln, so you can run agents against it safely.

FAQ

Questions about trigger_bed_level

What does the trigger_bed_level tool do? +

Trigger a bed leveling / mesh probe on the printer. 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 trigger_bed_level? +

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

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

Can I rate-limit trigger_bed_level? +

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

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

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