This record as markdown: /tools/airmang-hwpx-mcp-server/get-table-map.md
What get_table_map does on Hwpx
AI agents call get_table_map to retrieve information from Hwpx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_table_map is rated Low
This tool retrieves metadata about tables within HWPX documents—their positions, dimensions, and contextual summaries. It performs a read-only query operation with no side effects on the document. While the server as a whole supports modification (Write tools like add_heading, add_paragraph exist), this specific tool is purely informational retrieval, placing it in the Read category with low severity.
From the tool's definition Tool name 'get_table_map' and description indicating it 'queries table location, size, and context summary in documents' (조회 = query/retrieve). No modification, deletion, or execution of code mentioned.
Attacks that exploit this kind of access
The rule that runs get_table_map 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 get_table_map, this is the rule to start with:
get_table_map is read-only, so it stays allowed. 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 get_table_map call is checked against it from then on.
Questions about get_table_map
문서 내 표 위치, 크기, 문맥 요약을 조회합니다. It is categorised as a Read tool in the Hwpx MCP Server, which means it retrieves data without modifying state.
Register the Hwpx MCP server in PolicyLayer and add a rule for get_table_map: 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.
get_table_map is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_table_map 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 get_table_map. 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.
get_table_map 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