This record as markdown: /tools/todos/approve-review-item.md
What approve_review_item does on Todos
AI agents use approve_review_item 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 approve_review_item is rated Medium
This tool modifies data (a review item's approval status) in a reversible manner (the approval could potentially be withdrawn or changed). It does not delete data, execute arbitrary code, move money, or trigger external operations with variable effects.
From the tool's definition Tool name 'approve_review_item' and description 'Approve a local review queue item' indicate modifying the state of a review item from pending/unapproved to approved status.
Attacks that exploit this kind of access
The rule that runs approve_review_item 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 approve_review_item, this is the rule to start with:
approve_review_item 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 approve_review_item call is checked against it from then on.
Questions about approve_review_item
Approve a local review queue item. 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 approve_review_item: 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.
approve_review_item 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 approve_review_item 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 approve_review_item. 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.
approve_review_item 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