get_project_details
AI agents call get_project_details 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.
The tool retrieves project details from a public database (NIH Reporter). This is a read-only operation with no side effects—it cannot create, modify, delete, or execute arbitrary code. Even with an empty description, the context of a research information API and sibling tool patterns confirm this is a simple data retrieval function.
From the tool's definition Tool name 'get_project_details' and server context indicate retrieval of existing NIH research project information. Server description emphasizes 'querying' and 'retrieving detailed information' from the NIH Reporter API.
Attacks that exploit this kind of access
get_project_details. 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_details: 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_details 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_details 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_details. 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_details is provided by the NIH Reporter MCP Server MCP server (jhalsey87/mcp_nih_reporter). 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 →