This record as markdown: /tools/creativelead-unclick/discogs-get-release.md
What discogs_get_release does on UnClick
AI agents call discogs_get_release 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 |
|---|---|---|---|
api_key | string | — | |
release_id | number | — |
Parameters from the server's own tool schema.
Why discogs_get_release is rated Low
This tool retrieves information about a music release from Discogs by its identifier. It performs a data lookup without modifying, creating, deleting, or executing any operations. The operation has no side effects and poses minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'discogs_get_release' and description 'Get a Discogs release by ID' indicate a retrieval operation. The verb 'Get' and the action of fetching data by ID are characteristic of read-only queries with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs discogs_get_release 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_get_release, this is the rule to start with:
discogs_get_release 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_get_release call is checked against it from then on.
Questions about discogs_get_release
Get a Discogs release by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
discogs_get_release accepts 2 parameters: api_key, release_id. 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_get_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 UnClick. Nothing to install.
discogs_get_release 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_get_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.
Set action: deny in the PolicyLayer policy for discogs_get_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.
discogs_get_release is provided by the UnClick MCP server (creativelead/unclick). 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