execute_existing_check · Pingera MCP Server MCP

WHAT IT DOES

What execute_existing_check does on Pingera MCP Server

AI agents invoke execute_existing_check to trigger actions in Pingera MCP Server. 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 execute_existing_check needs a policy

The tool executes external monitoring operations whose effects depend on which check is selected as an argument. While the description is empty (lowering confidence slightly), the name and context clearly indicate this performs Execute-category actions: triggering remote checks against infrastructure.

From the tool's definition Tool name 'execute_existing_check' indicates execution of a pre-configured monitoring check. The verb 'execute' combined with context of a monitoring service (evidenced by sibling tools like create_check, create_alert, create_dns_check, create_heartbeat,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_existing_check Rate-limited

execute_existing_check 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": {
    "execute_existing_check": {
      "limits": [
        {
          "counter": "execute_existing_check_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 Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_existing_check

What does the execute_existing_check tool do? +

execute_existing_check. It is categorised as a Execute tool in the Pingera MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_existing_check? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for execute_existing_check: 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 execute_existing_check? +

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

Can I rate-limit execute_existing_check? +

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

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

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