batch_create_cliff_vesting · Basis MCP Server MCP

WHAT IT DOES

What batch_create_cliff_vesting does on Basis MCP Server

AI agents use batch_create_cliff_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 batch_create_cliff_vesting needs a policy

This tool creates vesting schedule records (cliff vestings) in batch, modifying contract state. While vesting creation is reversible (vesting parameters could be modified via sibling tools), it commits tokens to time-locked schedules and affects fund distribution logic.

From the tool's definition Tool name 'batch_create_cliff_vesting' combined with description 'Batch create cliff vestings' indicates the tool creates vesting agreements, which are reversible data structures on-chain. The batch operation multiplies scope but remains a creation action.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_create_cliff_vesting Rate-limited

batch_create_cliff_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": {
    "batch_create_cliff_vesting": {
      "limits": [
        {
          "counter": "batch_create_cliff_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 batch_create_cliff_vesting

What does the batch_create_cliff_vesting tool do? +

Batch create cliff vestings. All share the same token, unlock_time, 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.

How do I enforce a policy on batch_create_cliff_vesting? +

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

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

Can I rate-limit batch_create_cliff_vesting? +

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

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

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