Updates an existing milestone.
AI agents use update_project_milestone to create or update resources in Linear MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Server environment.
This tool modifies an existing project milestone but does not delete or irreversibly destroy it. It is reversible (can be updated again) and has no financial implications. The blast radius is moderate—incorrect updates could affect project planning and team coordination, but the changes can be corrected.
From the tool's definition Tool name is 'update_project_milestone' and description states 'Updates an existing milestone.' The verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
Updates an existing milestone. It is categorised as a Write tool in the Linear MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for update_project_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 Linear MCP Server. Nothing to install.
update_project_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_project_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_project_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_project_milestone is provided by the Linear MCP Server MCP server (sylphxai/linear-mcp). 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 →