list_remove

THE RISK

Critical Risk

Why list_remove needs a policy

The tool removes entries from a list, which is a modification/deletion operation. However, the description is vague — it's unclear whether this is reversible (Write) or irreversible (Destructive). 'Remove' typically implies deletion without an undo mechanism, so Destructive is chosen, but confidence is low due to the sparse description.

From the tool's definition 'Remove occurrences of value from list' — removes data from a list structure

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

POLICY

How to control list_remove

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

policy.json

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

list_remove 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 Finch MCP Server — 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 Finch MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 Finch MCP Server 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 Finch MCP Server → 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 list_remove

What does the list_remove tool do? +

Remove occurrences of value from list. It is categorised as a Destructive tool in the Finch MCP Server 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 list_remove? +

Register the Finch MCP Server MCP server in PolicyLayer and add a rule for list_remove: 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 Finch MCP Server. Nothing to install.

What risk level is list_remove? +

list_remove 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 list_remove? +

Yes. Add a rate_limit block to the list_remove 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 list_remove completely? +

Set action: deny in the PolicyLayer policy for list_remove. 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 list_remove? +

list_remove is provided by the Finch MCP Server MCP server (awslabs.finch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Finch MCP Server tool call.

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

CHECK YOUR STACK →