batch_create_gradual_vesting
Batch create gradual vesting schedules. All share the same token, start_time, duration, time_unit, ecosystem.
This record as markdown: /tools/launch-on-basis-mcp-ts/batch-create-gradual-vesting.md
What batch_create_gradual_vesting does on Basis MCP Server
AI agents use batch_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.
Why batch_create_gradual_vesting is rated Medium
This tool creates vesting schedules, which are financial configurations that modify token distribution rights. While it creates records (Write category) rather than executing arbitrary code or deleting data, the batch nature and financial context (vesting schedules control token release) elevate it to high severity.
From the tool's definition Tool name 'batch_create_gradual_vesting' and description 'Batch create gradual vesting schedules' indicate creation of multiple vesting schedule records. The 'create' verb and batch operation confirm data creation without irreversible deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_create_gradual_vesting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_create_gradual_vesting, this is the rule to start with:
batch_create_gradual_vesting stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every batch_create_gradual_vesting call is checked against it from then on.
Questions about batch_create_gradual_vesting
Batch create gradual vesting schedules. All share the same token, start_time, duration, time_unit, ecosystem. 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 batch_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.
batch_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 batch_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 batch_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.
batch_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.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue