list_milestones
AI agents call list_milestones to retrieve information from Clink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix is a strong indicator of a read-only query operation that retrieves or enumerates data without side effects. Even though the description is uninformative, the naming convention and context within a project/milestone management system support classification as Read. Confidence is slightly reduced due to empty description, but the tool name itself provides clear evidence.
From the tool's definition Tool name 'list_milestones' indicates a retrieval operation. The description is empty, but the naming pattern and sibling tools (create_milestone, create_project, check_inbox) suggest this lists existing milestones without modification.
Attacks that exploit this kind of access
list_milestones. It is categorised as a Read tool in the Clink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for list_milestones: 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.
list_milestones is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_milestones 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 list_milestones. 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.
list_milestones 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 →