New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

nihreporter.projects.by_pi

Find NIH-funded research projects by principal investigator (PI) last name. Optionally narrow by first name, fiscal year, or active status. Returns the researcher's funded projects with award amounts, institutions, titles, and abstract excerpts. Useful for biosketches, grant history lookups, and ...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nihreporter.projects.by-pi.md

What nihreporter.projects.by_pi does on Apibase

AI agents call nihreporter.projects.by_pi 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.

ParameterTypeRequiredDescription
limit integer — Number of results to return (1–25, default 10)
offset integer — Pagination offset — number of results to skip (default 0)
is_active boolean — When true, return only currently active/ongoing projects
last_name string Yes Principal investigator last name (e.g. "BHATT", "FAUCI", "COLLINS"). Case-insensitive, automatically uppercased.
first_name string — Principal investigator first name for disambiguation (optional, automatically uppercased)
fiscal_year integer — Fiscal year to filter (e.g. 2024). NIH fiscal year runs Oct 1 – Sep 30

Parameters from the server's own tool schema.

Why nihreporter.projects.by_pi is rated Low

Tool queries public NIH funding database; retrieves information with no side effects or data modification.

From the tool's definition Find NIH-funded research projects, returns researcher's funded projects with award amounts.

Questions about nihreporter.projects.by_pi

What does the nihreporter.projects.by_pi tool do? +

Find NIH-funded research projects by principal investigator (PI) last name. Optionally narrow by first name, fiscal year, or active status. Returns the researcher's funded projects with award amounts, institutions, titles, and abstract excerpts. Useful for biosketches, grant history lookups, and conflict-of-interest checks. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does nihreporter.projects.by_pi accept? +

nihreporter.projects.by_pi accepts 6 parameters: limit, offset, is_active, last_name, first_name, fiscal_year. Required: last_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nihreporter.projects.by_pi? +

Register the Apibase MCP server in PolicyLayer and add a rule for nihreporter.projects.by_pi: 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.

What risk level is nihreporter.projects.by_pi? +

nihreporter.projects.by_pi is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nihreporter.projects.by_pi? +

Yes. Add a rate_limit block to the nihreporter.projects.by_pi 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.

How do I block nihreporter.projects.by_pi completely? +

Set action: deny in the PolicyLayer policy for nihreporter.projects.by_pi. 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.

What MCP server provides nihreporter.projects.by_pi? +

nihreporter.projects.by_pi 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.