Get real-time status of a specific monitor. Returns current status, last check time, response time, and error message if any. Common use cases: - 'What's the status of api.example.com?' - 'Is monitor 42 up or down?' - 'When was the last check?' Returns: status, last_check_at, response_time_ms, ...
Single-target operation
Part of the PingZen Uptime Monitoring MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_monitor_status to retrieve information from PingZen Uptime Monitoring without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_monitor_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_monitor_status:
rules:
- action: allowSee the full PingZen Uptime Monitoring policy for all 44 tools.
Agents calling read-class tools like get_monitor_status have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get real-time status of a specific monitor. Returns current status, last check time, response time, and error message if any. Common use cases: - 'What's the status of api.example.com?' - 'Is monitor 42 up or down?' - 'When was the last check?' Returns: status, last_check_at, response_time_ms, http_status_code, error_message.. It is categorised as a Read tool in the PingZen Uptime Monitoring MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_monitor_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PingZen Uptime Monitoring MCP server.
get_monitor_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_monitor_status 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 get_monitor_status. 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.
get_monitor_status 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