update_status_page

Update an existing Status Page in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_status_page afterwards to see the updated record.

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 121 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-status-page.md

WHAT IT DOES

What update_status_page does on OneUptime

AI agents use update_status_page 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 Status Page to update. Required. Use list_status_pages to find IDs.
`name`	string	—	Any friendly name of this object.
`theme`	string	—	How the status page looks to visitors: Light, Dark, or System (light or dark, as each visitor's device is set). A status page created without a theme starts wit
`labels`	array	—	Relation to Labels Array where this object is categorized in.
`customCSS`	string	—	Status Page Custom CSS. Served only from a verified custom domain.
`pageTitle`	string	—	Title of your Status Page. This is used for SEO.
`footerHTML`	string	—	Status Page Custom HTML Footer. Served only from a verified custom domain.
`headerHTML`	string	—	Status Page Custom HTML Header. Served only from a verified custom domain.
`isArchived`	boolean	—	Archived status pages are hidden from the Status Pages list, are not served to visitors, and send nothing to their subscribers. Unarchiving puts them back onlin
`logoFileId`	string	—	Status Page Logo File ID.
`description`	string	—	Friendly description that will help you remember.
`ipWhitelist`	string	—	IP Whitelist for this Status Page. One IP per line. Only used if the status page is private.

Parameters from the server's own tool schema.

RISK

Why update_status_page is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_status_page Rate-limited

update_status_page 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_status_page": {
      "limits": [
        {
          "counter": "update_status_page_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_status_page call is checked against it from then on.

FAQ

Questions about update_status_page

What does the update_status_page tool do? +

Update an existing Status Page in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_status_page 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_status_page accept? +

update_status_page accepts 12 parameters: id, name, theme, labels, customCSS, pageTitle, footerHTML, headerHTML, isArchived, logoFileId, description, ipWhitelist. 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_status_page? +

Register the OneUptime MCP server in PolicyLayer and add a rule for update_status_page: 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_status_page? +

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

Can I rate-limit update_status_page? +

Yes. Add a rate_limit block to the update_status_page 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_status_page completely? +

Set action: deny in the PolicyLayer policy for update_status_page. 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_status_page? +

update_status_page 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 →