acknowledge_incident
Acknowledge an incident: marks it as being worked on by moving it to the project's 'Acknowledged' state. Equivalent to pressing 'Acknowledge' in the OneUptime dashboard. An incident that is already acknowledged - in the Acknowledged state, a state placed after it, or resolved - is left as it is.
This record as markdown: /tools/com-oneuptime-mcp/acknowledge-incident.md
What acknowledge_incident does on OneUptime
AI agents call acknowledge_incident to retrieve information from OneUptime without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
incidentId | string | Yes | UUID of the incident to acknowledge. Use list_incidents to find it. |
Parameters from the server's own tool schema.
Why acknowledge_incident is rated Low
Even though acknowledge_incident only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs acknowledge_incident 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 acknowledge_incident, this is the rule to start with:
acknowledge_incident is read-only, so it stays allowed. 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 acknowledge_incident call is checked against it from then on.
Questions about acknowledge_incident
Acknowledge an incident: marks it as being worked on by moving it to the project's 'Acknowledged' state. Equivalent to pressing 'Acknowledge' in the OneUptime dashboard. An incident that is already acknowledged - in the Acknowledged state, a state placed after it, or resolved - is left as it is. It is categorised as a Read tool in the OneUptime MCP Server, which means it retrieves data without modifying state.
acknowledge_incident accepts 1 parameter: incidentId. Required: incidentId. 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 acknowledge_incident: 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.
acknowledge_incident is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the acknowledge_incident 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 acknowledge_incident. 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.
acknowledge_incident 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