create_alert

Create New Relic alert condition

SERVERNcp SOURCE@portel/ncp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/create-alert.md

WHAT IT DOES

What create_alert does on Ncp

AI agents use create_alert to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.

RISK

Why create_alert is rated Medium

This tool creates a new monitoring alert condition in New Relic, which is a reversible write operation. It modifies system state by adding configuration but does not execute arbitrary code, delete data, or move money. The blast radius is medium because misconfiguration of alerts could cause notification spam or missed critical alerts, but the operation itself is non-destructive and can be undone.

From the tool's definition Tool is named 'create_alert' and described as 'Create New Relic alert condition'. The verb 'Create' indicates a write operation that generates new data/configuration in New Relic.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_alert safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_alert, this is the rule to start with:

create_alert Rate-limited

create_alert 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": {
    "create_alert": {
      "limits": [
        {
          "counter": "create_alert_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every create_alert call is checked against it from then on.

FAQ

Questions about create_alert

What does the create_alert tool do? +

Create New Relic alert condition. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_alert? +

Register the Ncp MCP server in PolicyLayer and add a rule for create_alert: 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 Ncp. Nothing to install.

What risk level is create_alert? +

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

Can I rate-limit create_alert? +

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

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

create_alert is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →