AI agents invoke require_approval_gate to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool is classified as Execute rather than Write because it doesn't simply create data (a checkpoint record), but rather implements a control flow mechanism that gates or triggers subsequent operations. The purpose is to enforce approval workflows before 'risky task or run work,' indicating it influences execution of other operations. While it creates a checkpoint, the primary function is operational control.
From the tool's definition 'Create a local manual approval checkpoint before risky task or run work' indicates this tool triggers an operation (checkpoint creation) that controls execution flow and gates subsequent work.
Attacks that exploit this kind of access
Create a local manual approval checkpoint before risky task or run work. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Todos MCP server in PolicyLayer and add a rule for require_approval_gate: 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.
require_approval_gate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the require_approval_gate 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 require_approval_gate. 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.
require_approval_gate 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →