Retrieve validator statistics via /api/v1/validators for Stargate NFT delegation decisions and validator performance. IMPORTANT: Look at all no status filter when getting validators when getting nft yields, when getting current validator not nft yields look at status=ACTIVE KEY METRICS: - nftYiel...
AI agents call getValidators 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.
Even though getValidators 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.
Attacks that exploit this kind of access
Retrieve validator statistics via /api/v1/validators for Stargate NFT delegation decisions and validator performance. IMPORTANT: Look at all no status filter when getting validators when getting nft yields, when getting current validator not nft yields look at status=ACTIVE KEY METRICS: - nftYieldsIfDelegatedNextCycle: Projected APY (%) for each Stargate NFT level in the next cycle if delegated to this validator (use this for delegation decisions) - nftYields: Current-cycle APY (%) for each Stargate NFT level already delegated to this validator - blockProbability: Validator. It is categorised as a Read tool in the VeChain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VeChain MCP Server MCP server in PolicyLayer and add a rule for getValidators: 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.
getValidators is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getValidators 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.
Set action: deny in the PolicyLayer policy for getValidators. 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.
getValidators 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.