get_vesting_count

Total vesting schedules created.

Server Basis MCP Server launch-on-basis/mcp-ts
Category Read
Risk class Low
Parameters 00 required

What get_vesting_count does on Basis MCP Server

AI agents call get_vesting_count to retrieve information from Basis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_vesting_count needs a policy

This tool retrieves read-only information about the number of vesting schedules. It performs no side effects, creates no transactions, and cannot modify or delete data. It is a simple data query operation, fitting the 'Read' category. Severity is low because misuse only exposes non-sensitive count information.

From the tool's definition Tool name 'get_vesting_count' and description 'Total vesting schedules created' indicate a query operation that retrieves aggregate count data without modifying state.

Questions about get_vesting_count

What does the get_vesting_count tool do? +

Total vesting schedules created. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_vesting_count? +

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

get_vesting_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_vesting_count? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.