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.
This record as markdown: /tools/com-oneuptime-mcp/update-security-case-priority.md
What update_security_case_priority does on OneUptime
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.
| 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 | — | What the priority is called, like High or P1. |
color | object | — | The priority's colour, in hex (#32a852 for example). |
order | integer | — | 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 | — | Archived priorities stay on the cases at them, but can't be picked again. The built-in priorities can't be archived. |
description | string | — | How fast a case at this priority needs a person, in a sentence. |
isLowPriority | boolean | — | Is it the priority Low detections open cases at? A project has one, and it can't be deleted or archived. |
isHighPriority | boolean | — | 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 | — | 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 | — | 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 | — | 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 | — | 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.
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 signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs update_security_case_priority 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 update_security_case_priority, this is the rule to start with:
update_security_case_priority stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_security_case_priority call is checked against it from then on.
Questions about 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. It is categorised as a Write tool in the OneUptime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_security_case_priority accepts 12 parameters: id, name, color, order, isArchived, description, isLowPriority, isHighPriority, isMediumPriority, isCriticalPriority, containWithinInMinutes, isInformationalPriority. Required: id. 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 update_security_case_priority: 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.
update_security_case_priority is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_security_case_priority 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 update_security_case_priority. 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.
update_security_case_priority 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