This record as markdown: /tools/todos/release-task-lease.md
What release_task_lease does on Todos
AI agents use release_task_lease 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 release_task_lease is rated Medium
Releasing a task lease modifies the state of a task (freeing it from a held/locked state), which is a reversible write operation. It doesn't delete data, execute code, or involve financial transactions. Misuse could disrupt task coordination for AI agents, hence medium severity.
From the tool's definition Release a held task lease
Attacks that exploit this kind of access
The rule that runs release_task_lease 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 release_task_lease, this is the rule to start with:
release_task_lease 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 release_task_lease call is checked against it from then on.
Questions about release_task_lease
Release a held task lease. 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 release_task_lease: 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.
release_task_lease 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_task_lease 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_task_lease. 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_task_lease 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