get_project_information
AI agents call get_project_information to retrieve information from NIH RePORTER MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project/award information from a public NIH grant database. No evidence suggests it modifies data, executes arbitrary code, deletes records, or handles financial transactions. It is a read-only data retrieval operation with minimal risk if misused by an AI agent—worst case being excessive or irrelevant queries to a public database.
From the tool's definition Tool name 'get_project_information' and server description indicating retrieval of 'detailed award information' from NIH's RePORTER database.
Attacks that exploit this kind of access
get_project_information. It is categorised as a Read tool in the NIH RePORTER MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NIH RePORTER MCP Server MCP server in PolicyLayer and add a rule for get_project_information: 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 NIH RePORTER MCP Server. Nothing to install.
get_project_information 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 get_project_information 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 get_project_information. 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.
get_project_information is provided by the NIH RePORTER MCP Server MCP server (pradeept95/nih-reporter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →