Get document metadata (version, page count, section count, fonts used, totals for tables/images/footnotes/equations/headers/footers). Args: file_path.
AI agents call get_hwp_info 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.
get_hwp_info performs a pure query operation that extracts and returns document structural information without creating, modifying, deleting, or executing any operations. The tool is explicitly read-only and poses minimal risk even if misused by an AI agent, as it cannot alter documents or trigger external effects.
From the tool's definition Tool description states it 'Get[s] document metadata' including 'version, page count, section count, fonts used, totals for tables/images/footnotes/equations/headers/footers'.
Documented attack patterns abuse exactly the kind of access get_hwp_info 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_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_hwp_info": {}
}
}get_hwp_info 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.
Get document metadata (version, page count, section count, fonts used, totals for tables/images/footnotes/equations/headers/footers). 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 get_hwp_info: 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.
get_hwp_info 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 get_hwp_info 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 get_hwp_info. 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.
get_hwp_info 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.