list_active_leases
List active task leases, optionally filtered by agent.
This record as markdown: /tools/todos/list-active-leases.md
What list_active_leases does on Todos
AI agents call list_active_leases to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_active_leases is rated Low
This tool retrieves and displays information about active task leases. It performs no mutations, executions, or deletions—purely a read operation to query the state of task leases in the system. The optional filtering parameter does not change this classification.
From the tool's definition Tool name 'list_active_leases' and description 'List active task leases, optionally filtered by agent' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_active_leases 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 list_active_leases, this is the rule to start with:
list_active_leases 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 Todos, apply this rule, and every list_active_leases call is checked against it from then on.
Questions about list_active_leases
List active task leases, optionally filtered by agent. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for list_active_leases: 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.
list_active_leases 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 list_active_leases 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 list_active_leases. 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.
list_active_leases 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