test_log_parsing_rule · Newrelic MCP: Risk & Policy

WHAT IT DOES

What test_log_parsing_rule does on Newrelic

AI agents invoke test_log_parsing_rule to trigger actions in Newrelic. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why test_log_parsing_rule needs a policy

Testing a parsing rule involves running/executing logic against sample data. While it may not persist changes, it actively executes a rule and processes data, placing it in the Execute category rather than Read. The blast radius is medium as misuse could expose log data or consume resources but is unlikely to cause irreversible damage.

From the tool's definition 'Test a log parsing rule against sample logs' — this triggers execution of a parsing rule against log data, an active operation with external side effects beyond simple data retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_log_parsing_rule Rate-limited

test_log_parsing_rule stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_log_parsing_rule": {
      "limits": [
        {
          "counter": "test_log_parsing_rule_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 test_log_parsing_rule

What does the test_log_parsing_rule tool do? +

Test a log parsing rule against sample logs. It is categorised as a Execute tool in the Newrelic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_log_parsing_rule? +

Register the Newrelic MCP server in PolicyLayer and add a rule for test_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 test_log_parsing_rule? +

test_log_parsing_rule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_log_parsing_rule? +

Yes. Add a rate_limit block to the test_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 test_log_parsing_rule completely? +

Set action: deny in the PolicyLayer policy for test_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 test_log_parsing_rule? +

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