get_location_text
get_table_map/find_text가 반환한 location으로 텍스트를 조회합니다.
This record as markdown: /tools/airmang-hwpx-mcp-server/get-location-text.md
What get_location_text does on Hwpx
AI agents call get_location_text 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_location_text is rated Low
This tool retrieves or queries text content from a HWPX document at specified locations. It is a read-only operation that returns data without creating, modifying, deleting, or executing any external operations. No reversible or irreversible changes are made to the document.
From the tool's definition Tool name 'get_location_text' and description 'get_table_map/find_text가 반환한 location으로 텍스트를 조회합니다' (retrieves text at a location). The verb '조회' means 'to query/retrieve' with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_location_text 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_location_text, this is the rule to start with:
get_location_text 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_location_text call is checked against it from then on.
Questions about get_location_text
get_table_map/find_text가 반환한 location으로 텍스트를 조회합니다. 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_location_text: 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_location_text 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_location_text 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_location_text. 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_location_text 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