Search for publications linked to NIH projects
AI agents call search_publications to retrieve information from NIH RePORTER MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the NIH RePORTER database to retrieve publication information associated with funded research projects. It performs a lookup/search operation with no side effects, no data modification, no code execution, and no destructive actions. The minimal blast radius if misused would be exposure of public NIH publication metadata. Confidence is high due to the clear read-only nature of the operation.
From the tool's definition Tool name 'search_publications' and description 'Search for publications linked to NIH projects' indicate data retrieval with no modification or execution. The verb 'search' is a classic read operation.
Attacks that exploit this kind of access
Search for publications linked to NIH projects. It is categorised as a Read tool in the NIH RePORTER MCP MCP Server, which means it retrieves data without modifying state.
Register the NIH RePORTER MCP server in PolicyLayer and add a rule for search_publications: 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. Nothing to install.
search_publications 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 search_publications 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 search_publications. 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.
search_publications is provided by the NIH RePORTER MCP server (jbdamask/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 →