create_milestone
AI agents use create_milestone to create or update resources in Clink MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clink MCP Server environment.
Creating a milestone is a write operation that adds new data to the project tracking system. While reversible (unlike destructive operations), it modifies the collaborative project state. Medium severity reflects that misuse could create misleading progress checkpoints affecting team coordination, but lacks the irreversibility of destructive operations or the severity of financial impact.
From the tool's definition Tool name 'create_milestone' indicates creation of a new entity. Server context shows milestone management capabilities for project tracking and multi-session collaboration. The empty description limits certainty.
Attacks that exploit this kind of access
create_milestone. It is categorised as a Write tool in the Clink MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for create_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 Clink MCP Server. Nothing to install.
create_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 create_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 create_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.
create_milestone is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). 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 →