This record as markdown: /tools/kiln/printer-files.md
What printer_files does on Kiln
AI agents call printer_files 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 printer_files is rated Low
The tool name indicates file querying or listing rather than file manipulation, creation, or execution. In the context of a 3D printer control server, accessing printer file metadata is a benign read operation. However, confidence is reduced due to the empty description—without explicit documentation, there is some uncertainty about whether this retrieves files, executes jobs, or has side effects.
From the tool's definition Tool name 'printer_files' suggests retrieval of file listings or metadata from a 3D printer. No description provided.
Attacks that exploit this kind of access
The rule that runs printer_files 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 printer_files, this is the rule to start with:
printer_files 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 printer_files call is checked against it from then on.
Questions about printer_files
printer_files 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 printer_files: 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.
printer_files 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 printer_files 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 printer_files. 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.
printer_files 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