Read full HWP/HWPX document content as text + tables (markdown) + image listing. Args: file_path (absolute path).
AI agents call read_hwp 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 retrieves and queries document content without side effects. It extracts text, tables, and image metadata from HWP/HWPX files for reading purposes only. No data is created, modified, deleted, or overwritten. This is a straightforward read operation with minimal risk.
From the tool's definition Tool name is 'read_hwp' and description states it 'Read[s] full HWP/HWPX document content as text + tables (markdown) + image listing' with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access read_hwp 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 read_hwp:
{
"version": "1",
"default": "deny",
"tools": {
"read_hwp": {}
}
}read_hwp 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.
Read full HWP/HWPX document content as text + tables (markdown) + image listing. Args: file_path (absolute path). 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 read_hwp: 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.
read_hwp 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 read_hwp 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 read_hwp. 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.
read_hwp 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.