nihreporter.projects.by_org
Find all NIH research grants awarded to a specific university, hospital, or research institute. Provide the institution name (partial uppercase match supported, e.g. "JOHNS HOPKINS", "MAYO CLINIC", "MIT"). Optionally filter by fiscal year or active status. Returns award amount, PI, title, and act...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nihreporter.projects.by-org.md
What nihreporter.projects.by_org does on Apibase
AI agents call nihreporter.projects.by_org 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) |
offset | integer | — | Pagination offset — number of results to skip (default 0) |
org_name | string | Yes | Institution or university name to search (e.g. "JOHNS HOPKINS UNIVERSITY", "HARVARD UNIVERSITY", "MAYO CLINIC"). Partial uppercase match. |
is_active | boolean | — | When true, return only currently active/ongoing projects |
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_org is rated Low
Retrieves publicly available NIH grant data; no modifications, deletions, or code execution involved.
From the tool's definition Find all NIH research grants, Returns award amount, PI, title
Attacks that exploit this kind of access
The rule that runs nihreporter.projects.by_org 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.by_org, this is the rule to start with:
nihreporter.projects.by_org 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.by_org call is checked against it from then on.
Questions about nihreporter.projects.by_org
Find all NIH research grants awarded to a specific university, hospital, or research institute. Provide the institution name (partial uppercase match supported, e.g. "JOHNS HOPKINS", "MAYO CLINIC", "MIT"). Optionally filter by fiscal year or active status. Returns award amount, PI, title, and activity code. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nihreporter.projects.by_org accepts 5 parameters: limit, offset, org_name, is_active, fiscal_year. Required: org_name. 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.by_org: 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.by_org 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.by_org 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.by_org. 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.by_org 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