update_monitor

Update an existing Monitor in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_monitor 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-monitor.md

WHAT IT DOES

What update_monitor does on OneUptime

AI agents use update_monitor 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 Monitor to update. Required. Use list_monitors to find IDs.
`name`	string	—	Any friendly name for this monitor.
`hosts`	array	—	Hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`labels`	array	—	Relation to Labels Array where this object is categorized in.
`services`	array	—	Services this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`iotFleets`	array	—	IoT fleets this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`isArchived`	boolean	—	Archived monitors are hidden from monitor lists and status pages, are not checked, and open no incidents or alerts. Unarchiving resumes monitoring.
`description`	string	—	Friendly description that will help you remember.
`dockerHosts`	array	—	Docker hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`podmanHosts`	array	—	Podman hosts this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`cephClusters`	array	—	Ceph clusters this monitor watches. Incidents and alerts it creates are linked to them, so OneUptime AI can investigate and fix them there.
`customFields`	object	—	Custom Fields on this resource.

Parameters from the server's own tool schema.

RISK

Why update_monitor is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_monitor Rate-limited

update_monitor 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_monitor": {
      "limits": [
        {
          "counter": "update_monitor_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_monitor call is checked against it from then on.

FAQ

Questions about update_monitor

What does the update_monitor tool do? +

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

update_monitor accepts 12 parameters: id, name, hosts, labels, services, iotFleets, isArchived, description, dockerHosts, podmanHosts, cephClusters, customFields. 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_monitor? +

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

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

Can I rate-limit update_monitor? +

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

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

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