This record as markdown: /tools/kh0pper-crow/rookery-search-openalex.md
What rookery_search_openalex does on Crow
AI agents call rookery_search_openalex 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 rookery_search_openalex is rated Low
The tool appears designed to query or search academic publication data from OpenAlex, a read-only academic database. The 'search' verb indicates data retrieval without modification. However, confidence is moderate due to the empty description—the actual implementation could involve side effects not evident from the name alone.
From the tool's definition Tool name contains 'search' and references 'openalex' (OpenAlex is a public academic metadata database). No description provided to confirm side effects.
Attacks that exploit this kind of access
The rule that runs rookery_search_openalex 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 rookery_search_openalex, this is the rule to start with:
rookery_search_openalex 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 rookery_search_openalex call is checked against it from then on.
Questions about rookery_search_openalex
rookery_search_openalex is a read tool on the Crow MCP server. 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 rookery_search_openalex: 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.
rookery_search_openalex 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 rookery_search_openalex 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 rookery_search_openalex. 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.
rookery_search_openalex 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