find_project_ids
AI agents call find_project_ids 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 appears to retrieve or query project identifiers from a public grants database. The empty description limits precision, but the naming convention ('find'), server context (searches and retrieves data), and sibling tools all indicate a read operation with no side effects. Even if misused by an AI agent, querying a public database for project IDs poses minimal risk.
From the tool's definition Tool name 'find_project_ids' and server description indicating it 'search and retrieve data from NIH's RePORTER grant database' with no mutations, deletions, or external operations described.
Attacks that exploit this kind of access
find_project_ids. 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 find_project_ids: 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.
find_project_ids 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 find_project_ids 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 find_project_ids. 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.
find_project_ids 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 →