Create gradual vesting schedule.
AI agents use create_gradual_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 new vesting schedule, which is a reversible modification of blockchain state. It does not execute arbitrary code, delete data irreversibly, or directly move funds, placing it in Write category. However, severity is high because vesting schedules control token release in financial contexts, and misconfiguration could lock tokens or grant unintended access to significant value.
From the tool's definition Tool creates a gradual vesting schedule, which modifies blockchain state by establishing a new vesting agreement. The description explicitly states 'Create gradual vesting schedule,' indicating data creation/modification.
Attacks that exploit this kind of access
Create gradual vesting schedule. 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_gradual_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_gradual_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_gradual_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_gradual_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_gradual_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 →