release_claim
Safely releases a stale open Boardroom todo from its current assignee so another worker can claim it. The server refuses fresh owners, protected human/manual work, in-progress work, unassigned work, capped reclaim attempts, and rows that changed during release. agent_id required.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/release-claim.md
What release_claim does on UnClick
AI agents use release_claim to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
todo_id | string | Yes | UUID of the stale open todo claim to release |
agent_id | string | Yes | Stable identifier for the calling agent. |
Parameters from the server's own tool schema.
Why release_claim is rated Medium
This tool writes/updates an assignment field on a todo item, removing the current assignee so another worker can claim it. It is reversible (another agent can claim it afterward) and does not delete data, making Write the appropriate category. Misuse could disrupt task workflows by releasing legitimate in-progress assignments, hence medium severity.
From the tool's definition 'Safely releases a stale open Boardroom todo from its current assignee so another worker can claim it' — modifies the assignment state of a task record
Attacks that exploit this kind of access
The rule that runs release_claim 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 release_claim, this is the rule to start with:
release_claim 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every release_claim call is checked against it from then on.
Questions about release_claim
Safely releases a stale open Boardroom todo from its current assignee so another worker can claim it. The server refuses fresh owners, protected human/manual work, in-progress work, unassigned work, capped reclaim attempts, and rows that changed during release. agent_id required. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
release_claim accepts 2 parameters: todo_id, agent_id. Required: todo_id, agent_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 release_claim: 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.
release_claim 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 release_claim 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 release_claim. 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.
release_claim 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