Create cliff vesting — all tokens unlock at once.
AI agents use create_cliff_vesting to create or update resources in Basis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
This tool creates a vesting schedule, which is a write operation that establishes a new financial arrangement. While it involves tokens and financial obligations, it does not move money immediately or commit irreversible transactions—it configures future token release terms.
From the tool's definition Tool description states 'Create cliff vesting — all tokens unlock at once.' The verb 'create' indicates reversible data creation/configuration. This is a financial contract setup tool that establishes token vesting schedules on a blockchain.
Attacks that exploit this kind of access
Create cliff vesting — all tokens unlock at once. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for create_cliff_vesting: 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.
create_cliff_vesting 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_cliff_vesting 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_cliff_vesting. 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_cliff_vesting 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 →