Soft-delete an observation by ID.
AI agents call mem_delete to permanently remove resources in Qontinui MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a delete operation on an observation. 'Soft-delete' implies the record is marked as deleted rather than permanently removed, which could be considered reversible, but since the primary action is deletion and the reversal mechanism is not described, it is categorized as Destructive. Severity is medium because soft-deletes are typically recoverable, limiting the blast radius.
From the tool's definition 'Soft-delete an observation by ID' — the tool deletes data by ID. Although described as a 'soft-delete' (which may be reversible depending on implementation), the primary action is deletion.
Attacks that exploit this kind of access
Soft-delete an observation by ID. It is categorised as a Destructive tool in the Qontinui MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for mem_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 Qontinui MCP Server. Nothing to install.
mem_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 mem_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 mem_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.
mem_delete is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-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 →