render_preview
레이아웃 충실 HTML과 headless browser PNG 프리뷰 산출물을 생성합니다.
This record as markdown: /tools/airmang-hwpx-mcp-server/render-preview.md
What render_preview does on Hwpx
AI agents use render_preview to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.
Why render_preview is rated Medium
An AI agent can call render_preview faster than any human can review: one bad instruction and it creates or modifies resources in Hwpx by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs render_preview safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_preview, this is the rule to start with:
render_preview stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every render_preview call is checked against it from then on.
Questions about render_preview
레이아웃 충실 HTML과 headless browser PNG 프리뷰 산출물을 생성합니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwpx MCP server in PolicyLayer and add a rule for render_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 Hwpx. Nothing to install.
render_preview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the render_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_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_preview is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hwpx, and thousands of servers like it.
This server
Across the catalogue