Permanently delete a StillOnline check. Use only when an endpoint should no longer be monitored.
AI agents call checks.delete to permanently remove resources in Stillonline — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a monitoring check is irreversible and cannot be undone. While not directly financial, the permanent removal of uptime monitoring infrastructure has high blast radius—an AI agent could inadvertently delete critical checks, leaving production endpoints unmonitored. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'
From the tool's definition Tool description explicitly states 'Permanently delete' a StillOnline check. The tool name includes 'delete' and the description confirms irreversible removal of a monitoring endpoint.
Attacks that exploit this kind of access
Permanently delete a StillOnline check. Use only when an endpoint should no longer be monitored. It is categorised as a Destructive tool in the Stillonline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stillonline MCP server in PolicyLayer and add a rule for checks.delete: 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 Stillonline. Nothing to install.
checks.delete 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 checks.delete 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 checks.delete. 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.
checks.delete is provided by the Stillonline MCP server (shenwell/stillonline-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 →