This record as markdown: /tools/todos/update-milestone.md
What update_milestone does on Todos
AI agents use update_milestone 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_milestone is rated Medium
This tool creates or modifies data reversibly. Updating a milestone changes project planning metadata but does not delete data or trigger external operations. The scope is local roadmap management, making it a Write operation with medium severity due to potential impact on project tracking and team coordination if misapplied by an agent.
From the tool's definition Tool name 'update_milestone' and description 'Update a local roadmap milestone' indicate modification of existing data. The word 'Update' is the key verb, and 'local roadmap milestone' is the resource being modified.
Attacks that exploit this kind of access
The rule that runs update_milestone 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_milestone, this is the rule to start with:
update_milestone 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_milestone call is checked against it from then on.
Questions about update_milestone
Update a local roadmap milestone. 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_milestone: 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_milestone 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_milestone 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_milestone. 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_milestone 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