Delete a log parsing rule
AI agents call delete_log_parsing_rule to permanently remove resources in Newrelic — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a log parsing rule configuration from New Relic. Deletion of log parsing rules cannot be undone and would cause immediate loss of that configuration, affecting any downstream log processing that depends on it. This is an irreversible operation meeting the Destructive category definition.
From the tool's definition Tool name is 'delete_log_parsing_rule' and description states 'Delete a log parsing rule'. The verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a log parsing rule. It is categorised as a Destructive tool in the Newrelic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Newrelic MCP server in PolicyLayer and add a rule for delete_log_parsing_rule: 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.
delete_log_parsing_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_log_parsing_rule 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 delete_log_parsing_rule. 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.
delete_log_parsing_rule 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 →