discogs_search_releases
Search for music releases on Discogs.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/discogs-search-releases.md
What discogs_search_releases does on UnClick
AI agents call discogs_search_releases to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | |
type | string | — | |
year | number | — | |
genre | string | — | |
artist | string | — | |
format | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why discogs_search_releases is rated Low
This tool performs a read-only search operation against the Discogs music database. It retrieves information about music releases but does not create, modify, delete, or execute any side effects. The search capability is a straightforward information retrieval function with no blast radius if misused by an AI agent.
From the tool's definition Tool is described as 'Search for music releases on Discogs' - the verb 'search' indicates a query operation that retrieves data without modifying it.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs discogs_search_releases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For discogs_search_releases, this is the rule to start with:
discogs_search_releases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every discogs_search_releases call is checked against it from then on.
Questions about discogs_search_releases
Search for music releases on Discogs. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
discogs_search_releases accepts 7 parameters: q, type, year, genre, artist, format, api_key. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for discogs_search_releases: 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 UnClick. Nothing to install.
discogs_search_releases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the discogs_search_releases 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.
Set action: deny in the PolicyLayer policy for discogs_search_releases. 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.
discogs_search_releases is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue