resolve_alert

Resolve an alert: moves it to the project's 'Resolved' state.

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-oneuptime-mcp/resolve-alert.md

WHAT IT DOES

What resolve_alert does on OneUptime

AI agents use resolve_alert 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
`alertId`	string	Yes	UUID of the alert to resolve. Use list_alerts to find it.

Parameters from the server's own tool schema.

RISK

Why resolve_alert is rated Medium

An AI agent can call resolve_alert 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_alert Rate-limited

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

FAQ

Questions about resolve_alert

What does the resolve_alert tool do? +

Resolve an alert: moves it to the project's 'Resolved' state. 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 resolve_alert accept? +

resolve_alert accepts 1 parameter: alertId. Required: alertId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_alert? +

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

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

Can I rate-limit resolve_alert? +

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

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

resolve_alert 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

resolve_projects on ACE-MCP →resolve_circuit on 0gzk → The MCP Attack Database →

Guides

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