Extract plain body text from an HWP/HWPX file (no tables, no images). Args: file_path.
AI agents call read_hwp_text 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 purely retrieves and extracts text content from a document with no side effects, modifications, or destructive operations. It is a straightforward read operation that queries document data without altering it.
From the tool's definition Tool name is 'read_hwp_text' and description states 'Extract plain body text from an HWP/HWPX file' with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access read_hwp_text 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_text:
{
"version": "1",
"default": "deny",
"tools": {
"read_hwp_text": {}
}
}read_hwp_text 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.
Extract plain body text from an HWP/HWPX file (no tables, no images). Args: file_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_text: 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_text 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_text 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_text. 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_text 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.