Get vesting schedule IDs for a token.
AI agents call get_token_vesting_ids to retrieve information from Basis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries vesting schedule information for a token without creating, modifying, deleting, executing code, or committing financial transactions. It is a simple data retrieval operation with no capability to alter state or trigger external actions. Low severity due to read-only nature and limited blast radius from misuse.
From the tool's definition Tool name 'get_token_vesting_ids' and description 'Get vesting schedule IDs for a token' indicate a retrieval/query operation with no side effects. The verb 'Get' and the action of fetching IDs from existing vesting schedules is purely informational.
Attacks that exploit this kind of access
Get vesting schedule IDs for a token. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_token_vesting_ids: 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 Basis MCP Server. Nothing to install.
get_token_vesting_ids 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_vesting_ids 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_vesting_ids. 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_vesting_ids is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →