get_session_status_live

Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.

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

What get_session_status_live does on XGR MCP Gateway

AI agents call get_session_status_live 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_session_status_live needs a policy

The tool performs a read-only query of session status information from the blockchain RPC endpoint. It retrieves existing data about session state without creating, modifying, deleting, or executing any on-chain actions. There is no financial exposure, no destructive potential, and no code execution involved.

From the tool's definition Tool description states it 'check[s] live session status from XGR RPC' and 'Returns xgr_sessionAlive for a session owner and session id.' This is a query operation that retrieves data without modification or side effects.

Questions about get_session_status_live

What does the get_session_status_live tool do? +

Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id. 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_session_status_live? +

Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_session_status_live: 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_session_status_live? +

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

Can I rate-limit get_session_status_live? +

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

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

get_session_status_live 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.