Search logs by field and value with optional time range. Supports wildcards (%) for pattern matching. Use this for targeted log searches based on specific criteria.
AI agents call query_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.
query_logs performs a search operation that retrieves log data based on filtering criteria. It does not create, modify, delete, execute code, or trigger external operations. The optional time range and wildcard support are query parameters that refine the search scope but do not change the fundamental read-only nature of the operation.
From the tool's definition Tool description states it "Search logs by field and value" and "Use this for targeted log searches based on specific criteria." The verb "search" and the read-only nature of querying logs without modification indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Search logs by field and value with optional time range. Supports wildcards (%) for pattern matching. Use this for targeted log searches based on specific criteria. 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 query_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.
query_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 query_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 query_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.
query_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 →