AI agents use update_log_parsing_rule to create or update resources in Newrelic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Newrelic environment.
This tool creates or modifies log parsing configuration reversibly. While it changes system behavior by altering how logs are processed, the change is reversible (the rule can be updated again or reverted). This is a Write operation rather than Execute because it modifies configuration data rather than triggering immediate operational actions.
From the tool's definition Tool name is 'update_log_parsing_rule' and description states 'Update an existing log parsing rule', which modifies configuration data in New Relic
Attacks that exploit this kind of access
Update an existing log parsing rule. It is categorised as a Write tool in the Newrelic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Newrelic MCP server in PolicyLayer and add a rule for update_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.
update_log_parsing_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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 →