get_started · Kiln MCP: Risk & Policy

WHAT IT DOES

What get_started does on Kiln

AI agents call get_started as a supporting operation in Kiln workflows.

WHY IT NEEDS A POLICY

Why get_started needs a policy

The description is empty and the name alone ('get_started') is ambiguous — it could be an onboarding/informational tool with no significant side effects. Without any description, confidence is very low. Defaulting to Other with low severity given the benign-sounding name and lack of evidence of destructive, financial, or execute-level behavior.

From the tool's definition Tool name is 'get_started' with an empty description. No actionable information about what this tool does.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

get_started Rate-limited

get_started gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_started": {
      "limits": [
        {
          "counter": "get_started_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR 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 get_started

What does the get_started tool do? +

get_started. It is categorised as a Other tool in the Kiln MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on get_started? +

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

get_started is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_started? +

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

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

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