move_release

Move a release instance to a different folder in your Discogs collection. Use search_collection to find release and instance IDs, and list_folders to see available folders.

ServerDiscogs MCP Server
CategoryWrite

How to control move_release ↓

WHAT IT DOES

What move_release does on Discogs MCP Server

AI agents use move_release to create or update resources in Discogs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discogs MCP Server environment.

THE RISK

Medium Risk

Why move_release needs a policy

The tool modifies existing data (folder assignment of a release) but does not delete data or execute arbitrary code. Moving between folders is reversible — the release can be moved back to its original location. This makes it a Write operation rather than Destructive or Execute.

From the tool's definition Tool description states 'Move a release instance to a different folder' — this modifies the organizational structure and metadata of a collection item by changing its folder location, which is a reversible write operation.

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

POLICY

How to control move_release

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 move_release:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_release": {
      "limits": [
        {
          "counter": "move_release_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

move_release stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT 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 Destructive remove_from_collection Remove a specific release instance from a folder in your Discogs collection. Use search_co 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

All 20 Discogs MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about move_release

What does the move_release tool do? +

Move a release instance to a different folder in your Discogs collection. Use search_collection to find release and instance IDs, and list_folders to see available folders. It is categorised as a Write tool in the Discogs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_release? +

Register the Discogs MCP Server MCP server in PolicyLayer and add a rule for move_release: 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 move_release? +

move_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_release? +

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

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

move_release 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 →

Free to start. No card required.

20 Discogs MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.