getCurrentRound

Get the current VeBetterDAO round ID by querying the X Allocation Voting smart contract directly. Rounds are time periods for voting cycles and reward distribution. Use this round ID to filter other queries (e.g., getB3TRGlobalOverview, getB3TRAppOverview) to see data for the current active round...

Server VeChain MCP Server vechain/vechain-mcp-server
Category Read
Risk class Low
Parameters 00 required

What getCurrentRound does on VeChain MCP Server

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

Why getCurrentRound needs a policy

Even though getCurrentRound only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about getCurrentRound

What does the getCurrentRound tool do? +

Get the current VeBetterDAO round ID by querying the X Allocation Voting smart contract directly. Rounds are time periods for voting cycles and reward distribution. Use this round ID to filter other queries (e.g., getB3TRGlobalOverview, getB3TRAppOverview) to see data for the current active round. Returns real-time on-chain value. It is categorised as a Read tool in the VeChain MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getCurrentRound? +

Register the VeChain MCP Server MCP server in PolicyLayer and add a rule for getCurrentRound: 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 VeChain MCP Server. Nothing to install.

What risk level is getCurrentRound? +

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

Can I rate-limit getCurrentRound? +

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

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

getCurrentRound is provided by the VeChain MCP Server MCP server (vechain/vechain-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.