create_alert · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_alert does on Pingera MCP Server

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

WHY IT NEEDS A POLICY

Why create_alert needs a policy

The 'create_' prefix indicates a data creation operation that is reversible (alerts can typically be deleted or modified). This is a Write rather than Execute because it appears to instantiate a monitoring configuration object rather than trigger arbitrary logic or external actions. The empty description lowers confidence slightly, but the naming convention and server context strongly suggest a Write operation.

From the tool's definition Tool name is 'create_alert' with an empty description. Based on sibling tools on the same Pingera monitoring server (create_check, create_component, create_heartbeat, create_dns_check, create_icmp_check, create_incident), this tool follows a clear pattern of…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about create_alert

What does the create_alert tool do? +

create_alert. It is categorised as a Write tool in the Pingera MCP Server 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 Pingera MCP Server 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 Pingera MCP Server. 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 Pingera MCP Server MCP server (pingera/pingera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.