AI agents call watch_print 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.
With no description available, classification is uncertain. The name 'watch_print' most plausibly refers to monitoring or observing an active 3D print job (a read/query operation). However, in a 3D printer control context, it could also trigger some active monitoring process. Confidence is low due to the empty description.
From the tool's definition Tool name 'watch_print' and empty description. 'Watch' typically implies monitoring/observing a print job.
Attacks that exploit this kind of access
watch_print. 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 watch_print: 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.
watch_print 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 watch_print 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 watch_print. 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.
watch_print 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 →