Semantic search across complete Hedera documentation. INDEXED: Official docs, SDK references (JS/Java/Go/Rust/Python), tutorials, HIPs, service specs RETURNS: Ranked results with titles, URLs, excerpts, relevance scores FILTERS: By content type (tutorial/api/concept/example), language, code prese...
AI agents call docs_search to retrieve information from HashPilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that searches and retrieves documentation content. It has no side effects, does not modify data, does not execute transactions or code, and does not affect blockchain state. The low severity reflects that misuse (e.g., agent repeatedly querying docs) poses minimal risk compared to account creation, balance transfers, or code execution tools on the same server.
From the tool's definition Tool performs 'Semantic search across complete Hedera documentation' and 'RETURNS: Ranked results with titles, URLs, excerpts, relevance scores'. It retrieves and queries information without modifying or executing any blockchain operations.
Attacks that exploit this kind of access
Semantic search across complete Hedera documentation. INDEXED: Official docs, SDK references (JS/Java/Go/Rust/Python), tutorials, HIPs, service specs RETURNS: Ranked results with titles, URLs, excerpts, relevance scores FILTERS: By content type (tutorial/api/concept/example), language, code presence USE FOR: Finding specific documentation, discovering relevant tutorials, locating API references. It is categorised as a Read tool in the HashPilot MCP Server, which means it retrieves data without modifying state.
Register the HashPilot MCP server in PolicyLayer and add a rule for docs_search: 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 HashPilot. Nothing to install.
docs_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 docs_search 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 docs_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.
docs_search is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →