openalex_search_works
Search OpenAlex for scholarly works by keyword.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openalex-search-works.md
What openalex_search_works does on UnClick
AI agents call openalex_search_works to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search term. |
per_page | number | — | Results per page (default 5, max 25). |
Parameters from the server's own tool schema.
Why openalex_search_works is rated Low
This tool retrieves or queries data from OpenAlex (an open bibliographic database) without side effects. It performs a read-only search operation. There is no indication of the ability to modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—returning unwanted search results poses no security risk.
From the tool's definition Tool name and description indicate a search operation: 'Search OpenAlex for scholarly works by keyword.' The verb 'search' and the context of querying a scholarly database (OpenAlex) with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs openalex_search_works safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openalex_search_works, this is the rule to start with:
openalex_search_works 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 UnClick, apply this rule, and every openalex_search_works call is checked against it from then on.
Questions about openalex_search_works
Search OpenAlex for scholarly works by keyword. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
openalex_search_works accepts 2 parameters: query, per_page. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openalex_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 UnClick. Nothing to install.
openalex_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 openalex_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 openalex_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.
openalex_search_works is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue