This record as markdown: /tools/kiln/kiln-health.md
What kiln_health does on Kiln
AI agents call kiln_health to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why kiln_health is rated Low
This tool retrieves diagnostic or status information about the Kiln system. It is a read-only operation with no side effects, no data modification, no code execution, and no destructive impact. The low severity reflects that health check data typically poses minimal risk if exposed to an AI agent, as it only provides observational information about system state.
From the tool's definition Tool name 'kiln_health' and description 'Get a health check for the Kiln system' indicate a query/retrieval operation that returns status information without modifying any state or triggering external actions.
Attacks that exploit this kind of access
The rule that runs kiln_health 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 kiln_health, this is the rule to start with:
kiln_health is read-only, so it stays allowed. 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 kiln_health call is checked against it from then on.
Questions about kiln_health
Get a health check for the Kiln system. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for kiln_health: 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.
kiln_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the kiln_health 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 kiln_health. 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.
kiln_health 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