Use this for high-level indexed XDaLa session analytics from the Explorer API.
AI agents call get_sessions_overview 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.
This tool retrieves session analytics data without side effects, placing it in the Read category. Severity is elevated to 'high' rather than 'low' because: (1) XDaLa sessions appear to represent significant on-chain state or activity; (2) the server description indicates access to blockchain transactions and contract data; (3) an AI agent querying session analytics could infer sensitive information about transaction…
From the tool's definition Tool name 'get_sessions_overview' and description 'high-level indexed XDaLa session analytics from the Explorer API' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Use this for high-level indexed XDaLa session analytics from the Explorer API. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_sessions_overview: 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.
get_sessions_overview 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_sessions_overview 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_sessions_overview. 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_sessions_overview 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.
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 →