stage_smoke_test

Open a small test cube on Kiln's 3D stage.

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/stage-smoke-test.md

WHAT IT DOES

What stage_smoke_test does on Kiln

AI agents invoke stage_smoke_test 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 stage_smoke_test is rated High

This tool executes an action against the 3D printer control software by loading/staging a test model. It is not merely reading data, nor does it delete anything or move money. It triggers an external operation whose effect is to open a test file in the 3D stage environment. Severity is low because it only stages a small test cube and does not initiate an actual print job.

From the tool's definition 'Open a small test cube on Kiln's 3D stage' — triggers an external operation (opening/staging a model) on the 3D printing software environment

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stage_smoke_test Rate-limited

stage_smoke_test 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": {
    "stage_smoke_test": {
      "limits": [
        {
          "counter": "stage_smoke_test_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 stage_smoke_test call is checked against it from then on.

FAQ

Questions about stage_smoke_test

What does the stage_smoke_test tool do? +

Open a small test cube on Kiln's 3D stage. 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 stage_smoke_test? +

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

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

Can I rate-limit stage_smoke_test? +

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

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

stage_smoke_test 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

advance_stage on 0sec →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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