// SCAN REPORT

Pingera MCP Server

79 tools. 44 can modify or destroy data without limits.

9 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

44 can modify or destroy data

35 read-only

79 tools total

Community server · catalogue entry verified 30/06/2026

How to control Pingera MCP Server ↓

TOOL MAP

What Pingera MCP Server exposes to your agents

Read (35) Write / Execute (35) Destructive / Financial (9)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pingera MCP Server tools

Destructive · High delete_alert The tool name 'delete_alert' explicitly indicates deletion of alert records. Destructive · High delete_check The tool deletes monitoring checks, which is an irreversible action. Destructive · High delete_check_group Deleting a check group is a destructive action that cannot be undone. Destructive · High delete_component The 'delete_component' tool performs an irreversible operation that removes monitoring infrastructure.

44 of Pingera MCP Server's 79 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pingera MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Pingera MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_alert": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_incident_update": {
    "limits": [
      {
        "counter": "add_incident_update_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_alert_details": {
    "limits": [
      {
        "counter": "get_alert_details_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pingera MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PINGERA →

Instant setup, no code required.

FULL CATALOGUE

All 79 Pingera MCP Server tools

DESTRUCTIVE 9 tools

Destructive delete_alert delete_alert Destructive delete_check delete_check Destructive delete_check_group Delete a check group. All checks in the group will be moved to ungrouped. Destructive delete_component delete_component Destructive delete_heartbeat delete_heartbeat Destructive delete_incident delete_incident Destructive delete_incident_update delete_incident_update Destructive delete_secret delete_secret Destructive remove_secret_from_check remove_secret_from_check

EXECUTE 8 tools

Execute execute_custom_check execute_custom_check Execute execute_dns_check execute_dns_check Execute execute_existing_check execute_existing_check Execute execute_icmp_check execute_icmp_check Execute execute_multistep_check execute_multistep_check Execute execute_synthetic_check execute_synthetic_check Execute generate_api_check_script generate_api_check_script Execute send_heartbeat_ping send_heartbeat_ping

WRITE 27 tools

Write add_incident_update add_incident_update Write add_secret_to_check add_secret_to_check Write assign_check_to_group assign_check_to_group Write create_alert create_alert Write create_check create_check Write create_check_group Create a new check group. Write create_component create_component Write create_dns_check create_dns_check Write create_heartbeat create_heartbeat Write create_icmp_check create_icmp_check Write create_incident create_incident Write create_multistep_check create_multistep_check Write create_secret create_secret Write create_synthetic_check create_synthetic_check Write generate_synthetic_check_script generate_synthetic_check_script Write patch_component patch_component Write patch_incident patch_incident Write resume_check resume_check Write update_alert update_alert Write update_check update_check Write update_check_group update_check_group Write update_check_secrets update_check_secrets Write update_component update_component Write update_heartbeat update_heartbeat Write update_incident update_incident Write update_incident_update update_incident_update Write update_secret Update a secret's value.

READ 35 tools

Read get_alert_details get_alert_details Read get_alert_statistics get_alert_statistics Read get_check_details get_check_details Read get_check_group_details Get detailed information about a specific check group. Read get_check_job_details get_check_job_details Read get_check_results get_check_results Read get_check_secrets get_check_secrets Read get_check_statistics get_check_statistics Read get_checks_in_group get_checks_in_group Read get_component_details get_component_details Read get_heartbeat_details get_heartbeat_details Read get_heartbeat_logs get_heartbeat_logs Read get_incident_details get_incident_details Read get_incident_update_details get_incident_update_details Read get_incident_updates get_incident_updates Read get_on_demand_job_status get_on_demand_job_status Read get_page_details get_page_details Read get_secret_details Get detailed information about a specific secret. Read get_unified_results get_unified_results Read get_unified_statistics get_unified_statistics Read list_alert_channels list_alert_channels Read list_alert_rules list_alert_rules Read list_alerts list_alerts Read list_check_groups list_check_groups Read list_check_jobs list_check_jobs Read list_checks list_checks Read list_component_groups list_component_groups Read list_components list_components Read list_heartbeats list_heartbeats Read list_incidents list_incidents Read list_on_demand_checks List on-demand checks. Read list_pages list_pages Read list_secrets list_secrets Read pause_check pause_check Read test_pingera_connection Test connection to Pingera API.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pingera MCP Server

Can an AI agent delete data through the Pingera MCP Server MCP server? +

Yes. The Pingera MCP Server server exposes 9 destructive tools including delete_alert, delete_check, delete_check_group. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pingera MCP Server? +

The Pingera MCP Server server has 27 write tools including add_incident_update, add_secret_to_check, assign_check_to_group. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pingera MCP Server.

How many tools does the Pingera MCP Server MCP server expose? +

79 tools across 4 categories: Destructive, Execute, Read, Write. 35 are read-only. 44 can modify, create, or delete data.

How do I enforce a policy on Pingera MCP Server? +

Register the Pingera MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pingera MCP Server tool call.

Deterministic rules across all 79 Pingera MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PINGERA →

Instant setup, no code required.

79 Pingera MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.