AI agents use set_task_contract 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.
This tool creates or modifies task contract specifications, which are configuration data that define how a task should be completed. While it influences task execution behavior through verification commands and done definitions, it does not directly execute external code, delete data irreversibly, or move money. The modifications are reversible through subsequent set_task_contract calls.
From the tool's definition The tool 'set_task_contract' modifies task metadata including 'acceptance criteria', 'verification commands', 'expected artifacts', 'relevant files', 'risk', and 'done definition'.
Attacks that exploit this kind of access
Set local task acceptance criteria, required verification commands, expected artifacts, relevant files, risk, and done definition. 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 set_task_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.
set_task_contract 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 set_task_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 set_task_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.
set_task_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 →