Set a custom field value on a release in your Discogs collection. Use list_custom_fields to see available fields and their IDs. For dropdown fields, the value must match one of the defined options.
AI agents use edit_custom_field 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.
This tool modifies metadata on a release record (setting custom field values) but does not delete, execute code, move money, or trigger external operations. It is a straightforward Write operation on user collection data with low blast radius since field edits are easily undone.
From the tool's definition Tool name 'edit_custom_field' and description 'Set a custom field value on a release' indicate data modification. The action is reversible—custom field values can be changed or cleared later.
Documented attack patterns abuse exactly the kind of access edit_custom_field gives an agent:
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 edit_custom_field:
{
"version": "1",
"default": "deny",
"tools": {
"edit_custom_field": {
"limits": [
{
"counter": "edit_custom_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} edit_custom_field 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.
Free to start. No card required.
Set a custom field value on a release in your Discogs collection. Use list_custom_fields to see available fields and their IDs. For dropdown fields, the value must match one of the defined options. 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.
Register the Discogs MCP Server MCP server in PolicyLayer and add a rule for edit_custom_field: 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.
edit_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit_custom_field 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 edit_custom_field. 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.
edit_custom_field 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.
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.
Free to start. No card required.
20 Discogs MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.