AI agents call diagnose_print_failure_live to retrieve information from Kiln without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates live diagnosis of print failures, which is consistent with querying printer state and logs for troubleshooting rather than executing commands or modifying printer settings. However, the empty description reduces confidence. In the context of 3D printer control, diagnostic tools typically retrieve telemetry and status information without side effects.
From the tool's definition Tool name 'diagnose_print_failure_live' suggests inspection/analysis of print status. Description is empty, limiting certainty.
Attacks that exploit this kind of access
diagnose_print_failure_live. 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 diagnose_print_failure_live: 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.
diagnose_print_failure_live 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 diagnose_print_failure_live 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 diagnose_print_failure_live. 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.
diagnose_print_failure_live 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 →