Delete the Mth row (0-based) from the Nth table (0-based) in an .hwpx. Args: file_path, table_index, row_index, output_path (optional).
AI agents call delete_hwp_table_row to permanently remove resources in Hwp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (table rows) from a document. While the document can theoretically be restored from backups, the deletion action itself cannot be undone by the tool, and an AI agent with access could permanently lose structured data. This qualifies as Destructive rather than Write (which is reversible).
From the tool's definition delete_hwp_table_row — the verb 'delete' and the tool's purpose to remove rows from a table document. The description explicitly states 'Delete the Mth row' from a table, which is an irreversible operation that cannot be undone through the tool itself.
Documented attack patterns abuse exactly the kind of access delete_hwp_table_row 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 delete_hwp_table_row:
{
"version": "1",
"default": "deny",
"hide": [
"delete_hwp_table_row"
]
} delete_hwp_table_row disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete the Mth row (0-based) from the Nth table (0-based) in an .hwpx. Args: file_path, table_index, row_index, output_path (optional). It is categorised as a Destructive tool in the Hwp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hwp MCP server in PolicyLayer and add a rule for delete_hwp_table_row: 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.
delete_hwp_table_row is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_hwp_table_row 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 delete_hwp_table_row. 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.
delete_hwp_table_row 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.