Low Risk

get_hwp_page_def

Get per-section page definition (paper size, margins, columns) and section properties. Useful for understanding document layout. Args: file_path.

How to control get_hwp_page_def ↓

AI agents call get_hwp_page_def 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 only retrieves and queries document structure information (paper size, margins, columns, section properties). It performs no writes, deletions, code execution, or financial operations. The verb 'Get' and framing as informational ('Useful for understanding') confirms it is a read-only query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_hwp_page_def' and description 'Get per-section page definition' and 'understanding document layout' indicate retrieval of metadata with no modification or side effects.

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

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

get_hwp_page_def 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 get_hwp_page_def tool do? +

Get per-section page definition (paper size, margins, columns) and section properties. Useful for understanding document layout. Args: file_path. 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 get_hwp_page_def? +

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

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

Can I rate-limit get_hwp_page_def? +

Yes. Add a rate_limit block to the get_hwp_page_def 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 get_hwp_page_def completely? +

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

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