change_vesting_beneficiary

Transfer vesting to new beneficiary.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/change-vesting-beneficiary.md

WHAT IT DOES

What change_vesting_beneficiary does on Basis MCP Server

AI agents use change_vesting_beneficiary 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.

RISK

Why change_vesting_beneficiary is rated Medium

This tool modifies the beneficiary of a vesting contract, reassigning who receives the vested tokens. This is a Write operation (modifying existing data/state) rather than Destructive since the vesting itself isn't deleted, just transferred.

From the tool's definition Transfer vesting to new beneficiary

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs change_vesting_beneficiary 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 change_vesting_beneficiary, this is the rule to start with:

change_vesting_beneficiary Rate-limited

change_vesting_beneficiary 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": {
    "change_vesting_beneficiary": {
      "limits": [
        {
          "counter": "change_vesting_beneficiary_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every change_vesting_beneficiary call is checked against it from then on.

FAQ

Questions about change_vesting_beneficiary

What does the change_vesting_beneficiary tool do? +

Transfer vesting to new beneficiary. 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 change_vesting_beneficiary? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for change_vesting_beneficiary: 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 change_vesting_beneficiary? +

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

Can I rate-limit change_vesting_beneficiary? +

Yes. Add a rate_limit block to the change_vesting_beneficiary 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 change_vesting_beneficiary completely? +

Set action: deny in the PolicyLayer policy for change_vesting_beneficiary. 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 change_vesting_beneficiary? +

change_vesting_beneficiary 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.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →