AI agents use append_hwp_table_column 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 and modifies document content (appending a table column) in a reversible manner. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), or handle financial transactions (which would be Financial).
From the tool's definition Tool name 'append_hwp_table_column' and description 'Append a new column to the Nth table in an .hwpx' indicate creation and modification of document structure.
Documented attack patterns abuse exactly the kind of access append_hwp_table_column 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 append_hwp_table_column:
{
"version": "1",
"default": "deny",
"tools": {
"append_hwp_table_column": {
"limits": [
{
"counter": "append_hwp_table_column_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}append_hwp_table_column 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.
Append a new column to the Nth table in an .hwpx. 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 append_hwp_table_column: 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.
append_hwp_table_column 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 append_hwp_table_column 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 append_hwp_table_column. 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.
append_hwp_table_column 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.