This record as markdown: /tools/todos/request-task-review.md
What request_task_review does on Todos
AI agents use request_task_review 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 request_task_review is rated Medium
Requesting a review creates or modifies a review state/record for a task. This is a Write operation as it initiates a new review request. It is reversible (reviews can be cancelled) and does not execute code, delete data, or involve finances. Medium severity since it affects task workflow state and could trigger notifications or assignments.
From the tool's definition 'Request local review for a task' - triggers a review request action
Attacks that exploit this kind of access
The rule that runs request_task_review 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 request_task_review, this is the rule to start with:
request_task_review 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 request_task_review call is checked against it from then on.
Questions about request_task_review
Request local review for a task. 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 request_task_review: 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.
request_task_review 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 request_task_review 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 request_task_review. 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.
request_task_review 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