# update_security_case_priority Update an existing Security Case Priority in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_priority afterwards to see the updated record. Agent View of the PolicyLayer registry record for `update_security_case_priority`. HTML page: https://policylayer.com/tools/com-oneuptime-mcp/update-security-case-priority ## Facts - Tool: `update_security_case_priority` - Server: OneUptime (`https://oneuptime.com/mcp`) — https://policylayer.com/tools/com-oneuptime-mcp.md - Homepage: https://github.com/OneUptime/oneuptime - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server CORS policy: * - Server rate-limited: no - Parameters: 12 (1 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | yes | The unique identifier (UUID) of the Security Case Priority to update. Required. Use list_security_case_priorities to find IDs. | | `name` | string | no | What the priority is called, like High or P1. | | `color` | object | no | The priority's colour, in hex (#32a852 for example). | | `order` | integer | no | Where this priority ranks among the project's security case priorities: 1 is the most urgent. Detections open their cases at the critical, high, medium, low and | | `isArchived` | boolean | no | Archived priorities stay on the cases at them, but can't be picked again. The built-in priorities can't be archived. | | `description` | string | no | How fast a case at this priority needs a person, in a sentence. | | `isLowPriority` | boolean | no | Is it the priority Low detections open cases at? A project has one, and it can't be deleted or archived. | | `isHighPriority` | boolean | no | Is it the priority High detections open cases at? From it up, a case counts as urgent. A project has one; it can't be deleted or archived. | | `isMediumPriority` | boolean | no | Is it the priority Medium detections, and the cases people open, start at? A project has one; it can't be deleted or archived. | | `isCriticalPriority` | boolean | no | Is it the priority Critical detections open cases at? From it up, a case can't wait. A project has one; it can't be deleted or archived. | | `containWithinInMinutes` | number | no | How long a case at this priority may take to be contained or closed, in minutes, from when it opens. Empty for no target. | | `isInformationalPriority` | boolean | no | Is it the priority Informational detections open cases at? A project has one, and it can't be deleted or archived. | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "update_security_case_priority", "arguments": { "id": "" } } } ``` ## Why update_security_case_priority is rated Medium An AI agent can call update_security_case_priority faster than any human can review: one bad instruction and it creates or modifies resources in OneUptime by the hundred, each call as confident as the last. Risk signals: High parameter count (13 properties) ## Use case AI agents use update_security_case_priority to create or update resources in OneUptime, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OneUptime environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches OneUptime: ```json { "version": "1", "default": "deny", "tools": { "update_security_case_priority": { "limits": [ { "counter": "update_security_case_priority_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on OneUptime (222) - `delete_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert.md - `delete_alert_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-internal-note.md - `delete_alert_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-severity.md - `delete_alert_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state.md - `delete_alert_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state-timeline.md - `delete_incident` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident.md - `delete_incident_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-alert.md - `delete_incident_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-internal-note.md - `delete_incident_public_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-public-note.md - `delete_incident_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-severity.md - `delete_incident_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state.md - `delete_incident_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state-timeline.md - `delete_label` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-label.md - `delete_monitor` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor.md - `delete_monitor_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status.md - `delete_monitor_status_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status-event.md - `delete_on_call_policy` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-on-call-policy.md - `delete_postmortem_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-postmortem-status.md - `delete_scheduled_maintenance_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-event.md - `delete_scheduled_maintenance_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state.md - `delete_scheduled_maintenance_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state-timeline.md - `delete_security_case` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case.md - `delete_security_case_evidence` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-evidence.md - `delete_security_case_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-note.md - `delete_security_case_priority` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-priority.md - `delete_security_case_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-status.md - `delete_security_case_task` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-task.md - `delete_security_detection` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-detection.md - `delete_security_playbook` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-playbook.md - `delete_status_page` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-status-page.md - …and 192 more: https://policylayer.com/tools/com-oneuptime-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-oneuptime-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-oneuptime-mcp