Search scholarly works in OpenAlex
AI agents call search_works to retrieve information from OpenAlex MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from OpenAlex's catalog of scholarly works without creating, modifying, deleting, or executing operations. It is a standard read operation with minimal risk—misuse would only return unwanted search results, not cause harm.
From the tool's definition Tool named 'search_works' with description 'Search scholarly works in OpenAlex'. The verb 'search' and context of querying a scholarly database indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search scholarly works in OpenAlex. It is categorised as a Read tool in the OpenAlex MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenAlex MCP Server MCP server in PolicyLayer and add a rule for search_works: 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 OpenAlex MCP Server. Nothing to install.
search_works 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_works 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_works. 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_works is provided by the OpenAlex MCP Server MCP server (reetp14/openalex-mcp). 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 →