Get detailed staking information and estimated rewards for a specific validator. Shows current stake (shares + tokens with accumulated rewards), validator commission, estimated APY (~12.5%), daily/monthly/yearly reward estimates, and share of validator stake. Read-only operation, no private key n...
AI agents call get_staking_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 state to display staking details, rewards, validator commission, and APY estimates. It has no side effects, does not modify data, and requires no authentication. The explicit 'read-only' label and absence of any write/execute/destructive capability place it firmly in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Read-only operation, no private key needed' and retrieves 'staking information and estimated rewards' without modifying state.
Attacks that exploit this kind of access
Get detailed staking information and estimated rewards for a specific validator. Shows current stake (shares + tokens with accumulated rewards), validator commission, estimated APY (~12.5%), daily/monthly/yearly reward estimates, and share of validator stake. Read-only operation, no private key 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_staking_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_staking_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_staking_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_staking_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_staking_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 →