run_benchmark · Kiln MCP: Risk & Policy

WHAT IT DOES

What run_benchmark does on Kiln

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

The 'run' verb combined with 'benchmark' indicates code/command execution rather than data retrieval or modification. Benchmarking typically involves triggering hardware diagnostics, stress tests, or performance measurements on the printer device. While the empty description creates some ambiguity, the pattern fits Execute (commands with external side effects) rather than Read, Write, or Destructive.

From the tool's definition Tool named 'run_benchmark' with no description provided. Given the server context (3D printer control via OctoPrint, Moonraker, Bambu, Prusa, Elegoo), 'run_benchmark' most likely executes performance tests or diagnostics on printer hardware/firmware,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_benchmark Rate-limited

run_benchmark 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_benchmark": {
      "limits": [
        {
          "counter": "run_benchmark_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 run_benchmark

What does the run_benchmark tool do? +

run_benchmark. 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_benchmark? +

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

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

Can I rate-limit run_benchmark? +

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

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

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