Low Risk

render_hwp_all_pages

Render every page of an HWP/HWPX as SVG files in a directory. Args: file_path, output_dir (default <file>_pages/), max_pages (optional limit).

How to control render_hwp_all_pages ↓

AI agents call render_hwp_all_pages 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.

Low Risk

This tool reads an HWP/HWPX document and renders its pages as SVG files. While it writes SVG output files to a directory, its primary purpose is extracting/converting content from an existing document for viewing. The output is a derived read-only representation. Severity is low as misuse would at most create SVG files in a specified directory.

From the tool's definition Render every page of an HWP/HWPX as SVG files in a directory

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access render_hwp_all_pages 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_all_pages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "render_hwp_all_pages": {}
  }
}

render_hwp_all_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Hwp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the render_hwp_all_pages tool do? +

Render every page of an HWP/HWPX as SVG files in a directory. Args: file_path, output_dir (default <file>_pages/), max_pages (optional limit). It is categorised as a Read tool in the Hwp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on render_hwp_all_pages? +

Register the Hwp MCP server in PolicyLayer and add a rule for render_hwp_all_pages: 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.

What risk level is render_hwp_all_pages? +

render_hwp_all_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit render_hwp_all_pages? +

Yes. Add a rate_limit block to the render_hwp_all_pages 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.

How do I block render_hwp_all_pages completely? +

Set action: deny in the PolicyLayer policy for render_hwp_all_pages. 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.

What MCP server provides render_hwp_all_pages? +

render_hwp_all_pages 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.

Enforce policy on every Hwp tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.