Delete a UI state from a project.
AI agents call delete_state to permanently remove resources in Qontinui Web MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes UI state configurations from a project, which cannot be undone. Deletion operations fall into the Destructive category as they irreversibly eliminate data. The high severity reflects that an AI agent could accidentally or maliciously remove critical UI automation states that may be essential to workflows, potentially breaking dependent automations and requiring manual restoration.
From the tool's definition Tool name is 'delete_state' and description states 'Delete a UI state from a project.' The verb 'delete' combined with 'from a project' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a UI state from a project. It is categorised as a Destructive tool in the Qontinui Web MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for delete_state: 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 Qontinui Web MCP Server. Nothing to install.
delete_state 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_state 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_state. 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_state is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-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 →