delete_monitor_status_event
Permanently delete a Monitor Status Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.
This record as markdown: /tools/com-oneuptime-mcp/delete-monitor-status-event.md
What delete_monitor_status_event does on OneUptime
AI agents call delete_monitor_status_event to permanently remove resources in OneUptime, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The unique identifier (UUID) of the Monitor Status Event to delete. This action is irreversible. |
Parameters from the server's own tool schema.
Why delete_monitor_status_event is rated Critical
An AI agent that decides to call delete_monitor_status_event doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from OneUptime is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_monitor_status_event 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 delete_monitor_status_event, this is the rule to start with:
delete_monitor_status_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every delete_monitor_status_event call is checked against it from then on.
Questions about delete_monitor_status_event
Permanently delete a Monitor Status Event from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion. It is categorised as a Destructive tool in the OneUptime MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_monitor_status_event accepts 1 parameter: id. Required: id. 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 delete_monitor_status_event: 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.
delete_monitor_status_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_monitor_status_event 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 delete_monitor_status_event. 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.
delete_monitor_status_event 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.
Across the catalogue