search_by_investigator

search_by_investigator

Server NIH Reporter MCP Server jhalsey87/mcp_nih_reporter
Category Read
Risk class Low
Parameters 00 required

What search_by_investigator does on NIH Reporter MCP Server

AI agents call search_by_investigator 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.

Why search_by_investigator needs a policy

This tool performs a read-only query operation against the NIH Reporter API to retrieve information about investigators and their associated projects. The NIH Reporter data is public scientific/grant information with no side effects. The tool name and server context clearly indicate search/retrieval functionality. No data modification, deletion, code execution, or financial transaction is involved.

From the tool's definition Tool name 'search_by_investigator' combined with server purpose of providing 'programmatic access to the NIH Reporter API for searching and retrieving detailed information' and sibling tools like 'search_projects' and 'get_project_details' indicate this…

Questions about search_by_investigator

What does the search_by_investigator tool do? +

search_by_investigator. It is categorised as a Read tool in the NIH Reporter MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_investigator? +

Register the NIH Reporter MCP Server MCP server in PolicyLayer and add a rule for search_by_investigator: 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.

What risk level is search_by_investigator? +

search_by_investigator is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_by_investigator? +

Yes. Add a rate_limit block to the search_by_investigator 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 search_by_investigator completely? +

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

search_by_investigator 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.