delete_slx
AI agents call delete_slx to permanently remove resources in RunWhen Platform MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs deletion, which is inherently irreversible and destructive. Even though the description is empty, the explicit 'delete_' verb in the function name combined with the platform context (where SLXs are likely critical service configuration objects) indicates this tool can permanently remove data without undo capability.
From the tool's definition Tool name is 'delete_slx' which indicates irreversible deletion of SLX objects (Service-Level Experiences/SLOs in RunWhen platform context). The 'delete_' prefix is a strong signal for destructive operations.
Attacks that exploit this kind of access
delete_slx. It is categorised as a Destructive tool in the RunWhen Platform MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for delete_slx: 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 RunWhen Platform MCP. Nothing to install.
delete_slx 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_slx 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_slx. 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_slx is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →