🗂️ Build position index for document elements (headings, paragraphs, tables). Creates a searchable index of all document elements with: - Unique ID - Element type (heading/paragraph/table/image) - Text preview (first 200 chars) - Section and element indices - Character offset - Heading level (i...
Bulk/mass operation — affects multiple targets
Part of the Hwpx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke build_position_index to trigger processes or run actions in Hwpx. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
build_position_index can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
build_position_index:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Hwpx policy for all 135 tools.
Agents calling execute-class tools like build_position_index have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
build_position_index is one of the high-risk operations in Hwpx. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
🗂️ Build position index for document elements (headings, paragraphs, tables). Creates a searchable index of all document elements with: - Unique ID - Element type (heading/paragraph/table/image) - Text preview (first 200 chars) - Section and element indices - Character offset - Heading level (if applicable) - Table info (rows, cols) for tables Use get_position_index to retrieve cached index, or call this to rebuild after modifications.. It is categorised as a Execute tool in the Hwpx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for build_position_index. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hwpx MCP server.
build_position_index is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_position_index rule in your Intercept 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 Intercept policy for build_position_index. 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.
build_position_index is provided by the Hwpx MCP server (hwpx-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.