Search NewRelic incidents with filtering by state, priority, and entity. Uses NRQL to query the NrAiIncident event type.
AI agents call search_incident to retrieve information from NewRelic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_incident retrieves and filters incident data from NewRelic without creating, modifying, deleting, or executing any actions. It is a pure query tool analogous to a database SELECT statement. The blast radius of misuse is minimal — an agent could retrieve sensitive incident information, but cannot cause operational harm through this tool alone.
From the tool's definition Tool description states it 'Search[es] NewRelic incidents' and 'query[s] the NrAiIncident event type' — these are read-only query operations with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Search NewRelic incidents with filtering by state, priority, and entity. Uses NRQL to query the NrAiIncident event type. It is categorised as a Read tool in the NewRelic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NewRelic MCP Server MCP server in PolicyLayer and add a rule for search_incident: 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 NewRelic MCP Server. Nothing to install.
search_incident 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_incident 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_incident. 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_incident is provided by the NewRelic MCP Server MCP server (ruminaider/newrelic-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 →