AI agents call list_trusted_printers 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 queries and returns configuration data (trusted printer list) without modifying, executing commands on, or destructively affecting any system. It is a straightforward read operation that retrieves information for informational purposes only. Even in a multi-printer environment, exposure of this list poses minimal security risk compared to tools that actually control printer hardware or execute code.
From the tool's definition Tool name is 'list_trusted_printers' and description states 'Return the list of trusted printer hostnames/IPs' — purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the list of trusted printer hostnames/IPs. 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 list_trusted_printers: 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.
list_trusted_printers 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 list_trusted_printers 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 list_trusted_printers. 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.
list_trusted_printers 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 →