add_tokens_to_vesting · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why add_tokens_to_vesting needs a policy

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

Recommended rule Ready

Verdict

add_tokens_to_vesting Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_tokens_to_vesting": {
      "limits": [
        {
          "counter": "add_tokens_to_vesting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Basis MCP Server, so you can run agents against it safely.

FAQ

Questions about add_tokens_to_vesting

What does the add_tokens_to_vesting tool do? +

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.

How do I enforce a policy on add_tokens_to_vesting? +

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.

What risk level is add_tokens_to_vesting? +

add_tokens_to_vesting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_tokens_to_vesting? +

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.

How do I block add_tokens_to_vesting completely? +

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.

What MCP server provides add_tokens_to_vesting? +

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.