This record as markdown: /tools/kiln/diagnose-mesh.md
What diagnose_mesh does on Kiln
AI agents call diagnose_mesh 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 diagnose_mesh is rated Low
The name 'diagnose_mesh' suggests a diagnostic/analysis operation on a mesh (likely a 3D printer bed mesh or 3D model mesh), which implies reading/querying data rather than modifying it. However, the empty description significantly lowers confidence. In the context of 3D printer control (OctoPrint/Moonraker), mesh diagnosis typically involves reading bed leveling mesh data.
From the tool's definition Tool name is 'diagnose_mesh'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs diagnose_mesh 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 diagnose_mesh, this is the rule to start with:
diagnose_mesh 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 diagnose_mesh call is checked against it from then on.
Questions about diagnose_mesh
diagnose_mesh is a read tool on the Kiln MCP server. 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_mesh: 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_mesh 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_mesh 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_mesh. 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_mesh 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