AI agents call list_synthetic_monitors to retrieve information from Newrelic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns monitoring configurations. It has no side effects, does not modify data, and poses minimal risk if misused by an AI agent—the worst outcome would be exposing the list of monitors configured in New Relic.
From the tool's definition Tool name 'list_synthetic_monitors' and description 'List all synthetic monitors' indicate a retrieval operation that enumerates existing synthetic monitors without modifying, deleting, or executing them.
Attacks that exploit this kind of access
List all synthetic monitors. It is categorised as a Read tool in the Newrelic MCP Server, which means it retrieves data without modifying state.
Register the Newrelic MCP server in PolicyLayer and add a rule for list_synthetic_monitors: 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. Nothing to install.
list_synthetic_monitors 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_synthetic_monitors 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_synthetic_monitors. 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_synthetic_monitors is provided by the Newrelic MCP server (@piekstras/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 →