This record as markdown: /tools/airmang-hwpx-mcp-server/table-compute.md
What table_compute does on Hwpx
AI agents use table_compute to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.
Why table_compute is rated Medium
The tool creates or modifies table data by inserting computed rows/columns. This is a reversible modification (rows can be deleted), not destructive deletion. It does not execute arbitrary code or trigger external operations—it performs a specific, bounded computation operation on document tables.
From the tool's definition Tool description indicates it 'adds sum/average/subtotal rows/columns to a general table' (일반 표에 합계·평균·소계 행/열을 추가). This modifies table structure and content within a HWPX document. The server description confirms tools 'modify HWPX documents directly'.
Attacks that exploit this kind of access
The rule that runs table_compute safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For table_compute, this is the rule to start with:
table_compute 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every table_compute call is checked against it from then on.
Questions about table_compute
일반 표에 합계·평균·소계 행/열을 추가하고 계산 근거를 반환합니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwpx MCP server in PolicyLayer and add a rule for table_compute: 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 Hwpx. Nothing to install.
table_compute 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 table_compute 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 table_compute. 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.
table_compute is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hwpx, and thousands of servers like it.
This server
Across the catalogue