Run an immediate health check for a monitor. Returns real-time result without waiting for the next scheduled check. The check is marked as manual (excluded from uptime SLA calculations). Common use cases: - 'Check if api.example.com is up right now' - 'Run a health check on monitor 42' Returns...
Part of the PingZen Uptime Monitoring MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke execute_check to trigger processes or run actions in PingZen Uptime Monitoring. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
execute_check can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
execute_check:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full PingZen Uptime Monitoring policy for all 44 tools.
Agents calling execute-class tools like execute_check have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
execute_check is one of the high-risk operations in PingZen Uptime Monitoring. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Run an immediate health check for a monitor. Returns real-time result without waiting for the next scheduled check. The check is marked as manual (excluded from uptime SLA calculations). Common use cases: - 'Check if api.example.com is up right now' - 'Run a health check on monitor 42' Returns: Check result with status, response time, errors.. It is categorised as a Execute tool in the PingZen Uptime Monitoring MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for execute_check. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PingZen Uptime Monitoring MCP server.
execute_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_check rule in your Intercept 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.
Set action: deny in the Intercept policy for execute_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.
execute_check is provided by the PingZen Uptime Monitoring MCP server (pingzen/uptime-monitoring). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept