Track upcoming token vesting unlock events that could create selling pressure on crypto assets. Returns unlock schedule, percentage of circulating supply, and estimated market impact. Use this tool when: - A crypto trading agent wants to avoid holding tokens with imminent large unlocks - You need...
AI agents call get_token_unlocks to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical and scheduled data about cryptocurrency token vesting events. While the parent server involves financial assets and crypto markets (increasing severity context), this specific tool only reads and returns analytical information—unlock schedules, percentages, and impact estimates. It does not execute trades, move funds, modify data, or trigger transactions.
From the tool's definition Tool description states it 'Track[s]' and 'Returns' data about token vesting schedules, unlock percentages, and market impact estimates. These are retrieval and query operations with no side effects.
Attacks that exploit this kind of access
Track upcoming token vesting unlock events that could create selling pressure on crypto assets. Returns unlock schedule, percentage of circulating supply, and estimated market impact. Use this tool when: - A crypto trading agent wants to avoid holding tokens with imminent large unlocks - You need to identify potential sell-pressure events before they hit the market - An agent is assessing whether a token. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_token_unlocks: 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 Omni Service Node. Nothing to install.
get_token_unlocks 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 get_token_unlocks 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 get_token_unlocks. 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.
get_token_unlocks is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →