This record as markdown: /tools/todos/list-pending-approvals.md
What list_pending_approvals does on Todos
AI agents call list_pending_approvals 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_pending_approvals is rated Low
This tool retrieves information about pending approvals without modifying, executing, or deleting any data. It is a straightforward read operation that returns status information to inform the user/agent about approval states. The minimal blast radius if misused (data disclosure of approval requests) places it in the low severity category.
From the tool's definition Tool name 'list_pending_approvals' and description 'List pending approval gate requests' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_pending_approvals 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_pending_approvals, this is the rule to start with:
list_pending_approvals 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_pending_approvals call is checked against it from then on.
Questions about list_pending_approvals
List pending approval gate requests. 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_pending_approvals: 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_pending_approvals 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_pending_approvals 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_pending_approvals. 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_pending_approvals 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