openaire.projects.search
Search OpenAIRE for funded research projects by free-text query across title, acronym, and keywords, e.g. "renewable energy" or "H2020". Returns project code, acronym, title, website, start/end dates, call identifier, keywords, summary, and funder details (funding body, jurisdiction, funding stre...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openaire.projects.search.md
What openaire.projects.search does on Apibase
AI agents call openaire.projects.search to retrieve information from Apibase 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1). |
query | string | — | Free-text search across project title, acronym, and keywords (e.g. "renewable energy", "H2020"). |
page_size | integer | — | Results per page (default 10, max 50). |
Parameters from the server's own tool schema.
Why openaire.projects.search is rated Low
Read-only search returning research project metadata with no side effects.
From the tool's definition Search OpenAIRE for funded research projects by free-text query
Attacks that exploit this kind of access
The rule that runs openaire.projects.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openaire.projects.search, this is the rule to start with:
openaire.projects.search 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 Apibase, apply this rule, and every openaire.projects.search call is checked against it from then on.
Questions about openaire.projects.search
Search OpenAIRE for funded research projects by free-text query across title, acronym, and keywords, e.g. "renewable energy" or "H2020". Returns project code, acronym, title, website, start/end dates, call identifier, keywords, summary, and funder details (funding body, jurisdiction, funding stream). Data: OpenAIRE Graph API, EU-funded open science infrastructure, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
openaire.projects.search accepts 3 parameters: page, query, page_size. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for openaire.projects.search: 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 Apibase. Nothing to install.
openaire.projects.search 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 openaire.projects.search 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 openaire.projects.search. 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.
openaire.projects.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue