AI agents call get_compatible_materials 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.
This tool retrieves or queries compatible materials data without modifying printer state, materials inventory, or triggering print operations. The absence of action verbs (add, delete, execute) suggests passive lookup. However, confidence is moderately reduced due to empty description—the tool could theoretically have side effects not apparent from the name alone.
From the tool's definition Tool name 'get_compatible_materials' indicates data retrieval of material compatibility information. No description provided, but the name structure (get_*) follows read-only query patterns seen in sibling tools like 'ams_status' which appear to fetch printer…
Attacks that exploit this kind of access
get_compatible_materials. 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 get_compatible_materials: 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.
get_compatible_materials 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 get_compatible_materials 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 get_compatible_materials. 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.
get_compatible_materials 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 →