unlock_task
Release a local task lock. The agent must own the active lock unless omitted for force release.
This record as markdown: /tools/todos/unlock-task.md
What unlock_task does on Todos
AI agents use unlock_task to create or update resources in Todos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
Why unlock_task is rated Medium
This tool modifies task lock state rather than permanently destroying data. While it could disrupt concurrent task management if misused (force releasing a lock owned by another agent), the effect is reversible—locks can be re-acquired. This makes it Write rather than Destructive or Execute.
From the tool's definition Tool description states 'Release a local task lock' and references 'force release' capability. The function modifies lock state (a form of state management) that controls task access and coordination.
Attacks that exploit this kind of access
The rule that runs unlock_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unlock_task, this is the rule to start with:
unlock_task 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 Todos, apply this rule, and every unlock_task call is checked against it from then on.
Questions about unlock_task
Release a local task lock. The agent must own the active lock unless omitted for force release. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for unlock_task: 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 Todos. Nothing to install.
unlock_task 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 unlock_task 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 unlock_task. 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.
unlock_task is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue