get_token_unlocks
Get upcoming token unlock schedule — cliff/linear vesting, USD value, supply impact. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-token-unlocks.md
What get_token_unlocks does on Crypto Intelligence
AI agents call get_token_unlocks to retrieve information from Crypto Intelligence without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Upcoming days to show (1-90) |
Parameters from the server's own tool schema.
Why get_token_unlocks is rated Low
This is a Read operation—it retrieves and queries historical/scheduled token unlock data. However, severity is elevated to medium rather than low because: (1) the server context involves real crypto trading and micropayments (x402), suggesting this intelligence directly informs financial decisions; (2) unlock schedules materially impact token prices and trading strategies; (3) if an AI agent receives inaccurate…
From the tool's definition Tool name 'get_token_unlocks' and description 'Get upcoming token unlock schedule — cliff/linear vesting, USD value, supply impact' indicate data retrieval with no side effects. The tool queries vesting schedules and supply projections.
Attacks that exploit this kind of access
The rule that runs get_token_unlocks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_token_unlocks, this is the rule to start with:
get_token_unlocks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crypto Intelligence, apply this rule, and every get_token_unlocks call is checked against it from then on.
Questions about get_token_unlocks
Get upcoming token unlock schedule — cliff/linear vesting, USD value, supply impact. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_token_unlocks accepts 1 parameter: days. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence 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 Crypto Intelligence. 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 Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue