AI agents call build_generation_prompt as a supporting operation in Kiln workflows.
With no description available, the most likely interpretation of 'build_generation_prompt' is that it assembles or constructs a prompt for use in a generation workflow — a read/construct operation with no obvious side effects. However, confidence is low due to the absence of any description.
From the tool's definition Tool description is empty and uninformative; tool name 'build_generation_prompt' suggests constructing a prompt string.
Attacks that exploit this kind of access
build_generation_prompt. It is categorised as a Other tool in the Kiln MCP Server, which means it performs auxiliary operations.
Register the Kiln MCP server in PolicyLayer and add a rule for build_generation_prompt: 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.
build_generation_prompt is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the build_generation_prompt 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 build_generation_prompt. 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.
build_generation_prompt 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →