list_security_case_statuses
List and search Security Case Statuses from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case Status objects plus the total matching count.
This record as markdown: /tools/com-oneuptime-mcp/list-security-case-statuses.md
What list_security_case_statuses does on OneUptime
AI agents call list_security_case_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 |
|---|---|---|---|
skip | number | — | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
sort | object | — | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
limit | number | — | Maximum number of records to return. Default: 10, Maximum: 100. |
query | object | — | Filter criteria for Security Case Statuses. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operato |
select | array | — | Optional: field names to return for each Security Case Status (e.g. ["_id", "name"]). Omit to get all readable fields. |
Parameters from the server's own tool schema.
Why list_security_case_statuses is rated Low
Even though list_security_case_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 (43 properties)
Attacks that exploit this kind of access
The rule that runs list_security_case_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 list_security_case_statuses, this is the rule to start with:
list_security_case_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 list_security_case_statuses call is checked against it from then on.
Questions about list_security_case_statuses
List and search Security Case Statuses from OneUptime with optional filtering, pagination, and sorting. Returns an array of Security Case Status objects plus the total matching count. It is categorised as a Read tool in the OneUptime MCP Server, which means it retrieves data without modifying state.
list_security_case_statuses accepts 5 parameters: skip, sort, limit, query, select. 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 list_security_case_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.
list_security_case_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 list_security_case_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 list_security_case_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.
list_security_case_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