nihreporter.projects.search
Search NIH-funded research projects by keyword, disease, drug, or technique. Returns up to 25 grants per call with PI names, institution, award amount, fiscal year, activity code (R01/U54/F32/etc.), abstract excerpt, and a URL to the full project on reporter.nih.gov. Filter by NIH institute/agenc...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nihreporter.projects.search.md
What nihreporter.projects.search does on Apibase
AI agents call nihreporter.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 |
|---|---|---|---|
limit | integer | — | Number of results to return (1–25, default 10) |
agency | string | — | NIH institute or agency code to filter by (e.g. "NCI" for cancer, "NIDDK" for diabetes, "NIMH" for mental health, "NIAID" for infectious disease) |
offset | integer | — | Pagination offset — number of results to skip (default 0) |
keyword | string | Yes | Research topic, disease, drug name, or technique to search (e.g. "mRNA cancer vaccine", "Alzheimer amyloid", "CRISPR") |
is_active | boolean | — | When true, return only currently active/ongoing projects |
fiscal_year | integer | — | Fiscal year to filter results (e.g. 2024). NIH fiscal year runs Oct 1 – Sep 30 |
Parameters from the server's own tool schema.
Why nihreporter.projects.search is rated Low
Queries public NIH grant database; retrieves data without side effects or modifications.
From the tool's definition Search NIH-funded research projects by keyword, disease, drug, or technique. Returns up to 25 grants per call.
Attacks that exploit this kind of access
The rule that runs nihreporter.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 nihreporter.projects.search, this is the rule to start with:
nihreporter.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 nihreporter.projects.search call is checked against it from then on.
Questions about nihreporter.projects.search
Search NIH-funded research projects by keyword, disease, drug, or technique. Returns up to 25 grants per call with PI names, institution, award amount, fiscal year, activity code (R01/U54/F32/etc.), abstract excerpt, and a URL to the full project on reporter.nih.gov. Filter by NIH institute/agency (e.g. NCI, NIDDK, NIAID, NIMH) and fiscal year. Sorted by award amount descending. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nihreporter.projects.search accepts 6 parameters: limit, agency, offset, keyword, is_active, fiscal_year. Required: keyword. 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 nihreporter.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.
nihreporter.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 nihreporter.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 nihreporter.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.
nihreporter.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