Merge vertical cells across rows in a single column by setting rowSpan on the first cell and removing absorbed cells in following rows. Args: file_path, table_index, col, row_start, row_count (>=2), output_path (optional).
AI agents use merge_hwp_cells_vertical 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.
The tool modifies document content by merging table cells—a structural change to a HWP document. This is a Write operation (modifies data reversibly) rather than Destructive because: (1) merging cells is reversible through unmerging or undo, (2) no data is permanently deleted, and (3) the operation can be undone.
From the tool's definition Tool description: 'Merge vertical cells across rows in a single column by setting rowSpan on the first cell and removing absorbed cells in following rows.' This modifies table structure by merging cells, which is a reversible alteration of document data.
Documented attack patterns abuse exactly the kind of access merge_hwp_cells_vertical 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 merge_hwp_cells_vertical:
{
"version": "1",
"default": "deny",
"tools": {
"merge_hwp_cells_vertical": {
"limits": [
{
"counter": "merge_hwp_cells_vertical_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_hwp_cells_vertical 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.
Merge vertical cells across rows in a single column by setting rowSpan on the first cell and removing absorbed cells in following rows. Args: file_path, table_index, col, row_start, row_count (>=2), output_path (optional). 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 merge_hwp_cells_vertical: 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.
merge_hwp_cells_vertical 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 merge_hwp_cells_vertical 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 merge_hwp_cells_vertical. 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.
merge_hwp_cells_vertical 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.