AI agents call check_orientation 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 name pattern 'check_' is consistent with read-only operations that retrieve printer state or design orientation without modification. Given the 3D printer control context and sibling tools that appear to query status, this is most likely a diagnostic read operation. Low severity because orientation checks do not modify hardware state or trigger physical actions. Confidence is reduced due to missing description.
From the tool's definition Tool name 'check_orientation' suggests a query/inspection operation typical of 3D printer control systems. Context shows tools like 'ams_status' and 'acquire_printer_lock' which are monitoring/state-checking operations. No description provided to confirm.
Attacks that exploit this kind of access
check_orientation. 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 check_orientation: 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.
check_orientation 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 check_orientation 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 check_orientation. 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.
check_orientation 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 →