This record as markdown: /tools/kh0pper-crow/crow-search-sources.md
What crow_search_sources does on Crow
AI agents call crow_search_sources to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_search_sources is rated Low
This tool performs a search operation to retrieve information from sources without creating, modifying, deleting, or executing anything. It is a read-only operation with minimal security risk—the worst outcome of misuse would be unauthorized access to information the user may not have intended to expose, but no data is altered or systems are compromised.
From the tool's definition Tool name 'crow_search_sources' and description 'Full-text search across all sources' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs crow_search_sources safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_search_sources, this is the rule to start with:
crow_search_sources 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 Crow, apply this rule, and every crow_search_sources call is checked against it from then on.
Questions about crow_search_sources
Full-text search across all sources. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_search_sources: 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 Crow. Nothing to install.
crow_search_sources 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 crow_search_sources 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 crow_search_sources. 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.
crow_search_sources is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue