Delete a monitor by ID
AI agents call delete_monitor to permanently remove resources in Uptrack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a monitor from the Uptrack system. Deletion is irreversible and represents loss of monitoring infrastructure and configuration. While the blast radius is somewhat contained (affects only that specific monitor), the action cannot be undone, placing it firmly in the Destructive category rather than Write.
From the tool's definition Tool name is 'delete_monitor' with description 'Delete a monitor by ID'. The verb 'delete' combined with the irreversible action of removing a monitoring configuration represents data destruction that cannot be undone.
Attacks that exploit this kind of access
Delete a monitor by ID. It is categorised as a Destructive tool in the Uptrack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Uptrack MCP server in PolicyLayer and add a rule for delete_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 Uptrack. Nothing to install.
delete_monitor 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 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. 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 is provided by the Uptrack MCP server (uptrack-app/uptrack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →