generate_log_parsing_rule · Newrelic MCP: Risk & Policy

WHAT IT DOES

What generate_log_parsing_rule does on Newrelic

AI agents use generate_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.

WHY IT NEEDS A POLICY

Why generate_log_parsing_rule needs a policy

The tool generates/creates a new log parsing rule, which is a configuration modification in New Relic. This is reversible via deletion (as evidenced by the delete_log_parsing_rule sibling), making it Write rather than Destructive. Medium severity because misconfigured parsing rules could affect log ingestion and analysis, but the blast radius is limited to logging configuration.

From the tool's definition Tool name 'generate_log_parsing_rule' and sibling tools 'create_log_parsing_rule' and 'delete_log_parsing_rule' indicate this tool creates or modifies log parsing configurations. Description is empty, reducing confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_log_parsing_rule Rate-limited

generate_log_parsing_rule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_log_parsing_rule": {
      "limits": [
        {
          "counter": "generate_log_parsing_rule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Newrelic, so you can run agents against it safely.

FAQ

Questions about generate_log_parsing_rule

What does the generate_log_parsing_rule tool do? +

generate_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.

How do I enforce a policy on generate_log_parsing_rule? +

Register the Newrelic MCP server in PolicyLayer and add a rule for generate_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.

What risk level is generate_log_parsing_rule? +

generate_log_parsing_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_log_parsing_rule? +

Yes. Add a rate_limit block to the generate_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.

How do I block generate_log_parsing_rule completely? +

Set action: deny in the PolicyLayer policy for generate_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.

What MCP server provides generate_log_parsing_rule? +

generate_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.