This record as markdown: /tools/kiln/job-history.md
What job_history does on Kiln
AI agents call job_history 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 job_history is rated Low
Job history retrieval is a read-only operation that queries past print jobs without modifying, deleting, or executing operations. Even in a 3D printer control context, accessing historical logs poses minimal risk—it does not move the printer, trigger prints, or irreversibly change state. Severity is low because the blast radius of accidental misuse is limited to information disclosure of past job metadata.
From the tool's definition Tool name 'job_history' suggests retrieval of historical job data from 3D printer systems (OctoPrint, Moonraker, Bambu, Prusa, Elegoo). The name pattern aligns with query/retrieval operations. Description is empty, reducing confidence.
Attacks that exploit this kind of access
The rule that runs job_history 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 job_history, this is the rule to start with:
job_history 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 job_history call is checked against it from then on.
Questions about job_history
job_history 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 job_history: 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.
job_history 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 job_history 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 job_history. 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.
job_history 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