run_benchmark

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 run_benchmark is rated High

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,…

The rule that runs run_benchmark 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_benchmark, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_benchmark": {
      "limits": [
        {
          "counter": "run_benchmark_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about run_benchmark