This record as markdown: /tools/airmang-hwpx-mcp-server/verify-toc.md
What verify_toc does on Hwpx
AI agents call verify_toc 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 verify_toc is rated Low
This tool performs validation/verification of cached page numbers in a table of contents and cross-references. Verification is a read-only operation that inspects data to confirm correctness without altering or modifying the document. No side effects occur beyond retrieving and checking information. This clearly falls under the Read category.
From the tool's definition Tool name 'verify_toc' and description '네이티브 차례/상호참조의 캐시 쪽번호를 검증합니다' (translates to 'verifies/validates cached page numbers of native table of contents/cross-references').
Attacks that exploit this kind of access
The rule that runs verify_toc 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 verify_toc, this is the rule to start with:
verify_toc 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 verify_toc call is checked against it from then on.
Questions about verify_toc
네이티브 차례/상호참조의 캐시 쪽번호를 검증합니다. 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 verify_toc: 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.
verify_toc 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 verify_toc 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 verify_toc. 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.
verify_toc 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