This record as markdown: /tools/todos/update-decision-record.md
What update_decision_record does on Todos
AI agents use update_decision_record 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 update_decision_record is rated Medium
This tool creates or modifies data (decision record fields) in a reversible way without deleting data or triggering external operations. The explicit exclusion of 'status' updates suggests it modifies metadata/content fields only. This fits the Write category.
From the tool's definition Tool name 'update_decision_record' and description 'Update decision record fields (not status)' indicates modifying existing data fields in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_decision_record 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 update_decision_record, this is the rule to start with:
update_decision_record 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 update_decision_record call is checked against it from then on.
Questions about update_decision_record
Update decision record fields (not status). 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 update_decision_record: 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.
update_decision_record 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 update_decision_record 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 update_decision_record. 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.
update_decision_record 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