This record as markdown: /tools/kiln/activate-license.md
What activate_license does on Kiln
AI agents use activate_license to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why activate_license is rated Medium
Activating a license key creates or modifies an entitlement/subscription record in the system. This is a Write operation (reversible state change — licenses can typically be deactivated). It is not Financial since no money is being moved directly, though misuse could commit a license seat. Severity is medium because an agent misusing this could activate unauthorized licenses or exhaust available license seats.
From the tool's definition Activate a Kiln Pro or Business license key
Attacks that exploit this kind of access
The rule that runs activate_license 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 activate_license, this is the rule to start with:
activate_license stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every activate_license call is checked against it from then on.
Questions about activate_license
Activate a Kiln Pro or Business license key. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for activate_license: 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.
activate_license is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the activate_license 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.
Set action: deny in the PolicyLayer policy for activate_license. 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.
activate_license 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.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue