update_on_call_policy

Update an existing On-Call Policy in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_on_call_policy afterwards to see the updated record.

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-oneuptime-mcp/update-on-call-policy.md

WHAT IT DOES

What update_on_call_policy does on OneUptime

AI agents use update_on_call_policy 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 On-Call Policy to update. Required. Use list_on_call_duty_policies to find IDs.
`name`	string	—	Any friendly name of this object.
`labels`	array	—	Relation to Labels Array where this object is categorized in.
`isArchived`	boolean	—	Archived on-call policies are hidden from the On-Call Policies list and page no one: incidents and alerts that use them skip them. Unarchiving puts them back in
`description`	string	—	Friendly description that will help you remember.
`customFields`	object	—	Custom Fields on this resource.
`acknowledgementTimeoutInMinutes`	number	—	Page again when something this policy paged about is acknowledged but not resolved within this many minutes (5 to 1440). Empty: never.
`repeatPolicyIfNoOneAcknowledges`	boolean	—	Repeat the policy if no one acknowledges the alert.
`repeatPolicyIfNoOneAcknowledgesNoOfTimes`	number	—	How many more times the policy starts again from its first escalation rule when nobody acknowledges: a whole number of 1 or more while Repeat Policy If No One A

Parameters from the server's own tool schema.

RISK

Why update_on_call_policy is rated Medium

An AI agent can call update_on_call_policy 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 (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_on_call_policy 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_on_call_policy, this is the rule to start with:

update_on_call_policy Rate-limited

update_on_call_policy 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_on_call_policy": {
      "limits": [
        {
          "counter": "update_on_call_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every update_on_call_policy call is checked against it from then on.

FAQ

Questions about update_on_call_policy

What does the update_on_call_policy tool do? +

Update an existing On-Call Policy in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_on_call_policy 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.

What parameters does update_on_call_policy accept? +

update_on_call_policy accepts 9 parameters: id, name, labels, isArchived, description, customFields, acknowledgementTimeoutInMinutes, repeatPolicyIfNoOneAcknowledges, repeatPolicyIfNoOneAcknowledgesNoOfTimes. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_on_call_policy? +

Register the OneUptime MCP server in PolicyLayer and add a rule for update_on_call_policy: 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.

What risk level is update_on_call_policy? +

update_on_call_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_on_call_policy? +

Yes. Add a rate_limit block to the update_on_call_policy 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.

How do I block update_on_call_policy completely? +

Set action: deny in the PolicyLayer policy for update_on_call_policy. 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.

What MCP server provides update_on_call_policy? +

update_on_call_policy 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.

KEEP EXPLORING

More on OneUptime, and thousands of servers like it.

This server

All 223 OneUptime tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →