get_account_live_state

Use this for live EVM account state. Returns balance, nonce and contract code for an address.

Server XGR MCP Gateway xgr-network/xgr-mcp
Category Read
Risk class Low
Parameters 00 required

What get_account_live_state does on XGR MCP Gateway

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

Why get_account_live_state needs a policy

This tool queries blockchain state (EVM account information) without creating, modifying, or deleting data. It is a read-only operation that retrieves public ledger information. The low severity reflects minimal blast radius: even if an AI agent misuses this tool, it can only access already-public blockchain data, with no financial, destructive, or execution implications.

From the tool's definition Tool name 'get_account_live_state' and description explicitly states it 'Returns balance, nonce and contract code for an address' — pure data retrieval with no modification or side effects.

Questions about get_account_live_state

What does the get_account_live_state tool do? +

Use this for live EVM account state. Returns balance, nonce and contract code for an address. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_live_state? +

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

What risk level is get_account_live_state? +

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

Can I rate-limit get_account_live_state? +

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

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

get_account_live_state is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-mcp). 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.