nsf-awards.grants.search
Search US National Science Foundation funded research awards by keyword, recipient institution name, US state, CFDA program number, and award date range. Returns award ID, title, awardee, principal investigator, dates, funding amount, program, and an abstract excerpt for each match. Data: api.nsf...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nsf-awards.grants.search.md
What nsf-awards.grants.search does on Apibase
AI agents call nsf-awards.grants.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 |
|---|---|---|---|
rpp | integer | — | Results per page, 1-25 (default 10). |
dateEnd | string | — | Only awards made on/before this date, format MM/DD/YYYY. |
keyword | string | — | Full-text search term matched against award title/abstract (e.g. "climate", "quantum computing"). |
dateStart | string | — | Only awards made on/after this date, format MM/DD/YYYY. |
cfdaNumber | string | — | Filter by CFDA program number (e.g. "47.070" for Computer and Information Science). |
awardeeName | string | — | Filter by recipient institution name substring (e.g. "Stanford", "MIT"). |
awardeeStateCode | string | — | Filter by recipient institution US state code, 2 letters (e.g. "CA", "NY"). |
Parameters from the server's own tool schema.
Why nsf-awards.grants.search is rated Low
Tool queries public NSF grant data without modifying, deleting, or executing actions with external side effects.
From the tool's definition Search US National Science Foundation funded research awards by keyword, returns award ID, title, awardee, dates, funding amount
Attacks that exploit this kind of access
The rule that runs nsf-awards.grants.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 nsf-awards.grants.search, this is the rule to start with:
nsf-awards.grants.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 nsf-awards.grants.search call is checked against it from then on.
Questions about nsf-awards.grants.search
Search US National Science Foundation funded research awards by keyword, recipient institution name, US state, CFDA program number, and award date range. Returns award ID, title, awardee, principal investigator, dates, funding amount, program, and an abstract excerpt for each match. Data: api.nsf.gov (National Science Foundation), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nsf-awards.grants.search accepts 7 parameters: rpp, dateEnd, keyword, dateStart, cfdaNumber, awardeeName, awardeeStateCode. 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 nsf-awards.grants.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.
nsf-awards.grants.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 nsf-awards.grants.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 nsf-awards.grants.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.
nsf-awards.grants.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