nsf-awards.grants.detail

Get full detail for a single NSF research award by award ID, including the complete abstract, principal investigator and co-PI contacts, program officer, directorate/division, funding by fiscal year, and award dates. Data: api.nsf.gov (National Science Foundation), no auth required.

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nsf-awards.grants.detail.md

WHAT IT DOES

What nsf-awards.grants.detail does on Apibase

AI agents call nsf-awards.grants.detail 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
`id`	string	Yes	NSF award ID, e.g. "2617572". Obtained from nsf-awards.search results.

Parameters from the server's own tool schema.

RISK

Why nsf-awards.grants.detail is rated Low

Retrieves public NSF award information; no modification, deletion, or external execution occurs.

From the tool's definition Get full detail for a single NSF research award, including abstract, contacts, dates

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nsf-awards.grants.detail 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.detail, this is the rule to start with:

nsf-awards.grants.detail Allowed

nsf-awards.grants.detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nsf-awards.grants.detail": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every nsf-awards.grants.detail call is checked against it from then on.

FAQ

Questions about nsf-awards.grants.detail

What does the nsf-awards.grants.detail tool do? +

What parameters does nsf-awards.grants.detail accept? +

nsf-awards.grants.detail accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nsf-awards.grants.detail? +

Register the Apibase MCP server in PolicyLayer and add a rule for nsf-awards.grants.detail: 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 nsf-awards.grants.detail? +

nsf-awards.grants.detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nsf-awards.grants.detail? +

Yes. Add a rate_limit block to the nsf-awards.grants.detail 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 nsf-awards.grants.detail completely? +

Set action: deny in the PolicyLayer policy for nsf-awards.grants.detail. 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 nsf-awards.grants.detail? +

nsf-awards.grants.detail 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →