This record as markdown: /tools/kh0pper-crow/search-datasets.md
What search_datasets does on Crow
AI agents call search_datasets 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 search_datasets is rated Low
This tool performs information retrieval from government data sources without modifying, deleting, or executing operations. The 'search' verb and lack of any side-effect language (create, delete, execute, update) place it squarely in the Read category. The blast radius is minimal—worst case, an AI agent retrieves publicly available government data, which carries low risk.
From the tool's definition Tool name 'search_datasets' and description 'Search for datasets across government sources' indicate a query/search operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs search_datasets 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 search_datasets, this is the rule to start with:
search_datasets 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 search_datasets call is checked against it from then on.
Questions about search_datasets
Search for datasets across government 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 search_datasets: 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.
search_datasets 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_datasets 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_datasets. 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_datasets 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