delete_list

THE RISK

Critical Risk

Why delete_list needs a policy

This tool permanently removes data (lists) without the possibility of recovery. While the blast radius is limited to list metadata rather than critical system files, the irreversible nature of deletion and the fact that it operates on user-created data structures classifies it as Destructive.

From the tool's definition Tool name is 'delete_list' with description 'Deletes an existing list by its ID.' The verb 'deletes' and the use case 'clean up lists that are no longer needed' clearly indicate irreversible data removal.

Documented attack patterns abuse exactly the kind of access delete_list gives an agent:

POLICY

How to control delete_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Par5, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_list:

policy.json

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

delete_list disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Par5 — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Par5 tools

Execute run_agent_across_list Spawns an AI coding agent for each item in a previously created list. Agents run in batche Execute run_shell_across_list Executes a shell command for each item in a previously created list. Commands run in batch Execute create_list_from_shell Creates a list by running a shell command and parsing its newline-delimited output. WHEN Write create_list Creates a named list of items for parallel processing. Use this tool when you need to perf Write update_list Updates an existing list by replacing its items with a new array. WHEN TO USE: - To modif Read get_list Retrieves the items in an existing list by its ID. WHEN TO USE: - To inspect the contents Read list_all_lists Lists all existing lists and their item counts. WHEN TO USE: - To see all available lists

All 8 Par5 tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Par5 → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_list

What does the delete_list tool do? +

Deletes an existing list by its ID. WHEN TO USE: - To clean up lists that are no longer needed - To free up memory after processing is complete. It is categorised as a Destructive tool in the Par5 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 Par5 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 Par5. 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 Par5 MCP server (mathematic-inc/par5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Par5 tool call.

Start from Par5, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →