Soft-delete a StillOnline project. Removes it from the dashboard and disables checks, matching the UI delete behavior.
AI agents call projects.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.
Although described as a 'soft-delete' rather than permanent destruction, the tool removes a project from the dashboard and disables all associated checks. This is a destructive action that cannot be easily undone by an AI agent and eliminates access to monitoring infrastructure. Soft-delete still qualifies as Destructive because it removes data from operational use irreversibly from the user's perspective.
From the tool's definition Tool name is 'projects.delete' and description states it 'Soft-delete a StillOnline project. Removes it from the dashboard and disables checks.' This is a deletion operation that irreversibly removes project data from active use.
Attacks that exploit this kind of access
Soft-delete a StillOnline project. Removes it from the dashboard and disables checks, matching the UI delete behavior. 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 projects.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.
projects.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 projects.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 projects.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.
projects.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.
projects.delete is one line of Stillonline's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →