This record as markdown: /tools/kiln/render-model-preview.md
What render_model_preview does on Kiln
AI agents call render_model_preview 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 render_model_preview is rated Low
With no description available, classification is based solely on the name. 'render_model_preview' most likely reads a 3D model and generates a preview image, which is a read/query operation with no destructive side effects. However, rendering could trigger compute-intensive operations. Confidence is low due to the empty description.
From the tool's definition Tool name 'render_model_preview' and empty description. The name suggests generating/rendering a preview image of a 3D model.
Attacks that exploit this kind of access
The rule that runs render_model_preview 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 render_model_preview, this is the rule to start with:
render_model_preview 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 render_model_preview call is checked against it from then on.
Questions about render_model_preview
render_model_preview 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 render_model_preview: 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.
render_model_preview 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 render_model_preview 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 render_model_preview. 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.
render_model_preview 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