List recent logs from NewRelic. Useful for getting an overview of recent log activity, filtering by level, or searching with custom conditions.
AI agents call list_recent_logs 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 log data without creating, modifying, deleting, or executing any operations. It performs filtering and searching on existing logs, which are characteristic of Read category tools. The blast radius is minimal since it only exposes observability data already available to authorized NewRelic users, with no side effects or state changes.
From the tool's definition Tool description states 'List recent logs from NewRelic' with operations for 'getting an overview of recent log activity, filtering by level, or searching with custom conditions.' These are purely read operations with no modification or deletion of data.
Attacks that exploit this kind of access
List recent logs from NewRelic. Useful for getting an overview of recent log activity, filtering by level, or searching with custom conditions. 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_logs: 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_logs 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_logs 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_logs. 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_logs 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 →