DELETE /v1/lists/{object_type}/{list_slug}. System lists cannot be deleted.
AI agents call delete_list to permanently remove resources in DataMerge MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes list data from the DataMerge system. Deletion is irreversible and cannot be undone. Even though system lists are protected from deletion, user-created lists can be destroyed without recovery options. The blast radius is high if an AI agent mistakenly or maliciously deletes important business lists.
From the tool's definition Tool name is 'delete_list' and description explicitly states 'DELETE /v1/lists/{object_type}/{list_slug}'. The HTTP method DELETE and the verb 'delete' in both the function name and endpoint confirm irreversible data removal.
Attacks that exploit this kind of access
DELETE /v1/lists/{object_type}/{list_slug}. System lists cannot be deleted. It is categorised as a Destructive tool in the DataMerge MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DataMerge MCP server in PolicyLayer and add a rule for delete_list: 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 DataMerge MCP. Nothing to install.
delete_list 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_list 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_list. 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_list is provided by the DataMerge MCP server (poolside-ventures/datamerge-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 →