search_docs
Search indexed documentation files (*.md, *.rst, *.txt) by semantic similarity.
This record as markdown: /tools/ashlesh-t-cognirepo/search-docs.md
What search_docs does on CogniRepo
AI agents call search_docs to retrieve information from CogniRepo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_docs is rated Low
This tool retrieves information from a static documentation index without creating, modifying, deleting, or executing any operations. It returns results based on semantic matching, which is a passive data retrieval pattern. The blast radius of misuse is minimal — an agent could retrieve irrelevant or excessive documentation, but cannot alter state, execute code, or cause harm.
From the tool's definition Tool performs 'Search indexed documentation files...by semantic similarity' — a retrieval operation with no modification or side effects. The verb 'search' and the read-only nature of querying indexed documentation confirm this is a Read operation.
Attacks that exploit this kind of access
The rule that runs search_docs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CogniRepo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_docs, this is the rule to start with:
search_docs 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 CogniRepo, apply this rule, and every search_docs call is checked against it from then on.
Questions about search_docs
Search indexed documentation files (*.md, *.rst, *.txt) by semantic similarity. It is categorised as a Read tool in the CogniRepo MCP Server, which means it retrieves data without modifying state.
Register the CogniRepo MCP server in PolicyLayer and add a rule for search_docs: 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 CogniRepo. Nothing to install.
search_docs 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_docs 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 search_docs. 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_docs is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue