Get comprehensive detailed information about a specific validator including staking metrics, commission rates, withdrawal fees, reward estimates, and performance calculations. Shows total staked, share ratios, APY estimates, and example reward calculations for different stake amounts (100 0G, 100...
AI agents call get_validator_info to retrieve information from 0g Chain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain data about validators and returns information to help users make staking decisions. It performs no state changes, creates no transactions, and modifies no data. The low severity reflects minimal risk if misused—an agent could only retrieve validator information, which is public blockchain data. No financial transactions, destructive operations, or code execution occur.
From the tool's definition Tool description explicitly states 'Read-only operation, no authentication needed' and retrieves 'comprehensive detailed information about a specific validator including staking metrics, commission rates, withdrawal fees, reward estimates, and performance…
Attacks that exploit this kind of access
Get comprehensive detailed information about a specific validator including staking metrics, commission rates, withdrawal fees, reward estimates, and performance calculations. Shows total staked, share ratios, APY estimates, and example reward calculations for different stake amounts (100 0G, 1000 0G). Useful for evaluating validators before staking. Read-only operation, no authentication needed. It is categorised as a Read tool in the 0g Chain MCP Server, which means it retrieves data without modifying state.
Register the 0g Chain MCP server in PolicyLayer and add a rule for get_validator_info: 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 0g Chain. Nothing to install.
get_validator_info 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 get_validator_info 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 get_validator_info. 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.
get_validator_info is provided by the 0g Chain MCP server (tairon-ai/0g-chain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →