List change events from NrChangeTracking. Includes deployments, configuration changes, and other tracked changes with version and user information.
AI agents call list_change_events 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 lists already-recorded change events from NewRelic's change tracking system. It performs a passive query operation with no side effects—it does not create, modify, delete, or execute operations. The data returned (deployments, configuration changes, version and user information) is informational only.
From the tool's definition Tool name 'list_change_events' and description 'List change events from NrChangeTracking' indicates retrieval/querying of historical change data. No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
List change events from NrChangeTracking. Includes deployments, configuration changes, and other tracked changes with version and user 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_change_events: 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_change_events 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_change_events 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_change_events. 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_change_events 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 →