generate_model · Kiln MCP: Risk & Policy

WHAT IT DOES

What generate_model does on Kiln

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

Given the context of a 3D printer control server with tools related to mesh manipulation, assembly, and printing, 'generate_model' likely triggers generation of a 3D model or initiates a computation/rendering process. This aligns with Execute (running an operation that produces output). However, the empty description significantly lowers confidence. It could also be Write if it merely saves a model file.

From the tool's definition Tool name 'generate_model' on a server for AI agent control of 3D printers; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_model Rate-limited

generate_model 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": {
    "generate_model": {
      "limits": [
        {
          "counter": "generate_model_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 generate_model

What does the generate_model tool do? +

generate_model. 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 generate_model? +

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

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

Can I rate-limit generate_model? +

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

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

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