This record as markdown: /tools/kiln/generate-print-certificate.md
What generate_print_certificate does on Kiln
AI agents use generate_print_certificate 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 generate_print_certificate is rated Medium
Generating certificates creates new data that could be stored or transmitted, making this a Write operation. Severity is medium because misuse could create fraudulent certificates (e.g., falsifying print job records or device credentials), but the blast radius is limited compared to financial or destructive operations.
From the tool's definition Tool name 'generate_print_certificate' suggests creation of a document or credential. The empty description prevents direct confirmation, but the verb 'generate' implies producing new data.
Attacks that exploit this kind of access
The rule that runs generate_print_certificate 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 generate_print_certificate, this is the rule to start with:
generate_print_certificate 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 generate_print_certificate call is checked against it from then on.
Questions about generate_print_certificate
generate_print_certificate is a write tool on the Kiln MCP server. 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 generate_print_certificate: 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.
generate_print_certificate 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 generate_print_certificate 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 generate_print_certificate. 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.
generate_print_certificate 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