AI agents call list_hwp_fields 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 queries and retrieves field information from HWP documents without creating, modifying, or deleting any content. It is a pure data retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'list_hwp_fields' and description indicate it lists/retrieves Hancom-style fields from HWP documents. The verb 'list' is a read-only operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_hwp_fields 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 list_hwp_fields:
{
"version": "1",
"default": "deny",
"tools": {
"list_hwp_fields": {}
}
}list_hwp_fields 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.
List Hancom-style fields (. 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 list_hwp_fields: 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.
list_hwp_fields 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 list_hwp_fields 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 list_hwp_fields. 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.
list_hwp_fields 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.