Performs full-text search on HexDocs documentation using Typesense search engine. This searches the actual documentation content across all packages on HexDocs. Note: If TideWave is available in your current Phoenix project, prefer using TideWave's documentation search for better project context...
Accepts freeform code/query input (query)
Part of the HexDocs MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call fulltext_search to retrieve information from HexDocs MCP 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 fulltext_search 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:
fulltext_search:
rules:
- action: allowSee the full HexDocs MCP policy for all 5 tools.
Agents calling read-class tools like fulltext_search 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.
Performs full-text search on HexDocs documentation using Typesense search engine. This searches the actual documentation content across all packages on HexDocs. Note: If TideWave is available in your current Phoenix project, prefer using TideWave's documentation search for better project context. Use this tool when TideWave is not available or for searching packages not in your current project. Query Syntax: - Basic search: "Phoenix.LiveView" (searches for both terms) - Exact phrase: "\"handle event\"" (use escaped quotes) - AND operator: "Phoenix AND LiveView" (both terms required) - OR operator: "Phoenix OR Plug" (either term) - Exclude terms: "Phoenix -test" (minus sign excludes) - Module/function: "Enum.map" or "GenServer.handle_call" Best Practices: - Use exact module.function names for precise results - Combine with packageName filter for focused search - Use quotes for multi-word exact phrases - For callbacks use patterns like "@callback handle_" - For types use patterns like "@type t()" Examples: - Find LiveView event handlers: query: "handle_event", packageName: "phoenix_live_view" - Find Ecto changesets: query: "changeset", packageName: "ecto" - Find specific function: query: "\"Enum.map/2\"" - Find type definitions: query: "@type", packageName: "phoenix". It is categorised as a Read tool in the HexDocs MCP MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for fulltext_search. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the HexDocs MCP MCP server.
fulltext_search 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 fulltext_search 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 fulltext_search. 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.
fulltext_search is provided by the HexDocs MCP MCP server (bradleygolden/hexdocs-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept