List recent AI-detected issues from NewRelic. Uses the experimental aiIssues API to fetch active and recent incidents with priority and state information.
AI agents call list_recent_issues 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.
This tool retrieves and queries incident data from NewRelic's experimental aiIssues API without side effects. It only reads information about existing incidents with their priority and state information. There is no capability to create, modify, delete incidents, or trigger external operations.
From the tool's definition Tool description states 'List recent AI-detected issues' and 'fetch active and recent incidents' — retrieval operations only. No mention of creating, modifying, deleting, or executing actions. The verb 'List' and 'fetch' indicate read-only data retrieval.
Attacks that exploit this kind of access
List recent AI-detected issues from NewRelic. Uses the experimental aiIssues API to fetch active and recent incidents with priority and state information. 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 list_recent_issues: 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.
list_recent_issues 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 list_recent_issues 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 list_recent_issues. 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.
list_recent_issues 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 →