AI agents use set_hwp_field_value to create or update resources in Hwp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwp environment.
This tool creates or modifies data within HWP documents reversibly. Setting field values in templates is a typical write operation that updates document content without permanent deletion or irreversible destruction. The scope is limited to field modification within an existing document structure, making it a Write rather than Execute or Destructive operation.
From the tool's definition Tool name 'set_hwp_field_value' indicates modification of document field values. Server description mentions 'fill templates' capability, which aligns with setting field values in HWP documents.
Documented attack patterns abuse exactly the kind of access set_hwp_field_value 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 set_hwp_field_value:
{
"version": "1",
"default": "deny",
"tools": {
"set_hwp_field_value": {
"limits": [
{
"counter": "set_hwp_field_value_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_hwp_field_value stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set a Hancom field. It is categorised as a Write tool in the Hwp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwp MCP server in PolicyLayer and add a rule for set_hwp_field_value: 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.
set_hwp_field_value is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_hwp_field_value 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 set_hwp_field_value. 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.
set_hwp_field_value 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.