remove_from_collection

THE RISK

Critical Risk

Why remove_from_collection needs a policy

This tool meets the definition of Destructive because it removes data irreversibly from the collection. While the impact is scoped to a single release instance (mitigating from critical to high severity), the action cannot be reversed without manual re-addition. The high severity reflects that an AI agent with misuse could permanently delete valuable collection entries.

From the tool's definition The tool 'remove_from_collection' performs an irreversible deletion operation: 'Remove a specific release instance from a folder in your Discogs collection.' This action cannot be undone and permanently deletes data from the user's collection.

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

POLICY

How to control remove_from_collection

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

policy.json

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

remove_from_collection 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 Discogs 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 Discogs MCP Server tools

Destructive delete_folder Delete a folder from your Discogs collection. The folder must be empty (no releases). Cann Execute refresh_collection Force an immediate full refresh of the cached collection snapshot. Use after adding or rem Write rate_release Rate a release in your Discogs collection from 0 (no rating) to 5 stars. Use search_collec Write add_to_collection Add a release to a folder in your Discogs collection. If no folder is specified, adds to t Write create_folder Create a new folder in your Discogs collection for organizing releases. Write edit_custom_field Set a custom field value on a release in your Discogs collection. Use list_custom_fields t Write edit_folder Rename an existing folder in your Discogs collection. Cannot rename the system folders (Al Write move_release Move a release instance to a different folder in your Discogs collection. Use search_colle

All 20 Discogs 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 Discogs 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 remove_from_collection

What does the remove_from_collection tool do? +

Remove a specific release instance from a folder in your Discogs collection. Use search_collection to find the instance_id for a release. It is categorised as a Destructive tool in the Discogs 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 remove_from_collection? +

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

What risk level is remove_from_collection? +

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

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

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

remove_from_collection is provided by the Discogs MCP Server MCP server (rianvdm/discogs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Discogs MCP Server tool call.

Start from Discogs 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 →