🔍 Search document chunks using BM25-based relevance scoring. Returns chunks ranked by similarity to query with: - Relevance score (higher = more relevant) - Matched search terms - Text snippet around first match - Full chunk data with position info Use for finding relevant sections in large do...
Accepts freeform code/query input (query); 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 call search_chunks to retrieve information from Hwpx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_chunks only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
search_chunks:
rules:
- action: allowSee the full Hwpx policy for all 135 tools.
Agents calling read-class tools like search_chunks have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
🔍 Search document chunks using BM25-based relevance scoring. Returns chunks ranked by similarity to query with: - Relevance score (higher = more relevant) - Matched search terms - Text snippet around first match - Full chunk data with position info Use for finding relevant sections in large documents without reading the entire content.. It is categorised as a Read tool in the Hwpx MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search_chunks. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hwpx MCP server.
search_chunks 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 search_chunks 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 search_chunks. 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.
search_chunks 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.