add_tokens_to_vesting
Add more tokens to existing vesting.
This record as markdown: /tools/launch-on-basis-mcp-ts/add-tokens-to-vesting.md
What add_tokens_to_vesting does on Basis MCP Server
AI agents use add_tokens_to_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 add_tokens_to_vesting is rated Medium
This tool modifies existing vesting records by adding tokens, which is a Write operation (creates or modifies data reversibly). It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and while it affects token distribution on a financial protocol, it is a modification rather than a direct money movement or subscription commitment (not strictly Financial per se, though it operates…
From the tool's definition Tool name 'add_tokens_to_vesting' and description 'Add more tokens to existing vesting' indicate modification of existing vesting schedules by appending tokens. This is a reversible write operation that alters state on a blockchain financial protocol.
Attacks that exploit this kind of access
The rule that runs add_tokens_to_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 add_tokens_to_vesting, this is the rule to start with:
add_tokens_to_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 add_tokens_to_vesting call is checked against it from then on.
Questions about add_tokens_to_vesting
Add more tokens to existing vesting. 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 add_tokens_to_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.
add_tokens_to_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 add_tokens_to_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 add_tokens_to_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.
add_tokens_to_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