Critical Risk →

delete_list

Delete a list by its ID.

Part of the Courier server.

delete_list can permanently delete data in Courier, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE COURIER →

Free to start. No card required.

AI agents may call delete_list to permanently remove or destroy resources in Courier. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_list in a loop, permanently destroying resources in Courier. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_list"
  ]
}

See the full Courier policy for all 123 tools.

Get this rule live on your own Courier server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COURIER →

View all 123 tools →

These attack patterns abuse exactly the kind of access delete_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so delete_list only ever does what you allow.

SECURE COURIER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the delete_list tool do? +

Delete a list by its ID.. It is categorised as a Destructive tool in the Courier MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_list? +

Register the Courier 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 Courier. Nothing to install.

What risk level is delete_list? +

delete_list is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_list? +

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.

How do I block delete_list completely? +

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.

What MCP server provides delete_list? +

delete_list is provided by the Courier MCP server (https://mcp.courier.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Courier tool call.

Deterministic rules across all 123 Courier tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.