return_review_item
Return a local review queue item with requested changes.
This record as markdown: /tools/todos/return-review-item.md
What return_review_item does on Todos
AI agents use return_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 return_review_item is rated Medium
This tool modifies the state of a review queue item by returning it with requested changes. This is a reversible write operation — it updates the status/content of a task review item rather than deleting it or executing code. Misuse could disrupt task workflows but is not irreversible.
From the tool's definition Return a local review queue item with requested changes
Attacks that exploit this kind of access
The rule that runs return_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 return_review_item, this is the rule to start with:
return_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 return_review_item call is checked against it from then on.
Questions about return_review_item
Return a local review queue item with requested changes. 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 return_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.
return_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 return_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 return_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.
return_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