AI agents call check_task_done_contract to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and validates the current state of a task against predefined requirements (the contract). It performs verification and comparison of existing data without modifying, deleting, executing commands, or moving money. The lack of any write, execute, or destructive operations, combined with the read-only nature of 'checking' status and evidence, clearly places this in the Read category with low severity.
From the tool's definition Tool name and description indicate checking/verifying task status against a contract: 'Check whether local task status, verification evidence, artifacts, and review state satisfy the task contract.' The verb 'check' combined with inspection of existing data…
Attacks that exploit this kind of access
Check whether local task status, verification evidence, artifacts, and review state satisfy the task contract. 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 check_task_done_contract: 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.
check_task_done_contract 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 check_task_done_contract 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 check_task_done_contract. 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.
check_task_done_contract 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 →