Search for NewRelic entities using tags and NerdGraph query syntax. Use this to find entities by environment, team, service name, or any custom tag.
AI agents call search_entity_with_tag 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.
The tool retrieves and queries NewRelic entities based on tag filters. It does not create, modify, delete, or execute any operations—it only searches and returns matching entity data. This is a classic Read category tool. Severity is low because searching for entities poses minimal risk; an AI agent could retrieve information about entities but cannot cause harm through search alone.
From the tool's definition Tool name is 'search_entity_with_tag' and description states it 'Search for NewRelic entities using tags and NerdGraph query syntax.' This performs a query/search operation to find entities, which is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for NewRelic entities using tags and NerdGraph query syntax. Use this to find entities by environment, team, service name, or any custom tag. 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 search_entity_with_tag: 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.
search_entity_with_tag 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 search_entity_with_tag 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 search_entity_with_tag. 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.
search_entity_with_tag 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 →