Render a single page of an HWP/HWPX as HTML. Useful for AI consumption when SVG isn
AI agents call render_hwp_html to retrieve information from Hwp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads/renders a page from an HWP/HWPX document and outputs it as HTML. It retrieves and transforms existing content without modifying the source file. No write, execute, or destructive operations are implied.
From the tool's definition Render a single page of an HWP/HWPX as HTML
Documented attack patterns abuse exactly the kind of access render_hwp_html gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hwp, and nothing reaches the server without passing your rules. This is the rule we recommend for render_hwp_html:
{
"version": "1",
"default": "deny",
"tools": {
"render_hwp_html": {}
}
}render_hwp_html is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Render a single page of an HWP/HWPX as HTML. Useful for AI consumption when SVG isn. It is categorised as a Read tool in the Hwp MCP Server, which means it retrieves data without modifying state.
Register the Hwp MCP server in PolicyLayer and add a rule for render_hwp_html: 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 Hwp. Nothing to install.
render_hwp_html 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_hwp_html 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_hwp_html. 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_hwp_html is provided by the Hwp MCP server (treesoop/hwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Hwp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
31 Hwp tools catalogued and risk-classified — across an index of 42,500+ MCP servers.