count_monitor_statuses
Count the total number of Monitor Statuses in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.
This record as markdown: /tools/com-oneuptime-mcp/count-monitor-statuses.md
What count_monitor_statuses does on OneUptime
AI agents call count_monitor_statuses to retrieve information from OneUptime without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | object | — | Optional filter criteria. If omitted, counts all Monitor Statuses. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", |
Parameters from the server's own tool schema.
Why count_monitor_statuses is rated Low
Even though count_monitor_statuses only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs count_monitor_statuses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OneUptime, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For count_monitor_statuses, this is the rule to start with:
count_monitor_statuses is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every count_monitor_statuses call is checked against it from then on.
Questions about count_monitor_statuses
Count the total number of Monitor Statuses in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing. It is categorised as a Read tool in the OneUptime MCP Server, which means it retrieves data without modifying state.
count_monitor_statuses accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.
Register the OneUptime MCP server in PolicyLayer and add a rule for count_monitor_statuses: 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 OneUptime. Nothing to install.
count_monitor_statuses 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 count_monitor_statuses 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.
Set action: deny in the PolicyLayer policy for count_monitor_statuses. 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.
count_monitor_statuses is provided by the OneUptime MCP server (https://oneuptime.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue