Use this to list recent indexed XDaLa sessions from the read-only Explorer database, especially when the user does not know owner and sessionId. Supports optional owner filtering, time windows, result limits and payload enrichment.
AI agents call get_recent_xdala_sessions 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 and queries session data from a read-only database without creating, modifying, deleting, or executing any operations. It is a straightforward Read category tool with low severity since it only accesses existing blockchain data without side effects or the ability to initiate any on-chain actions.
From the tool's definition Tool description explicitly states 'list recent indexed XDaLa sessions from the read-only Explorer database' and supports 'optional owner filtering, time windows, result limits and payload enrichment'.
Attacks that exploit this kind of access
Use this to list recent indexed XDaLa sessions from the read-only Explorer database, especially when the user does not know owner and sessionId. Supports optional owner filtering, time windows, result limits and payload enrichment. 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_recent_xdala_sessions: 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_recent_xdala_sessions 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_recent_xdala_sessions 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_recent_xdala_sessions. 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_recent_xdala_sessions 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 →