Use this when the user asks for the latest XDaLa session but does not provide owner and sessionId. This read-only tool resolves the newest indexed XDaLa session from the Explorer database and can optionally include final receipt payload data.
AI agents call find_latest_xdala_session 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 performs data retrieval only—querying blockchain session data from an indexed database. There are no state changes, deletions, financial transactions, or code execution involved. The read-only designation and retrieval-only nature clearly place it in the Read category with low severity, as it has minimal blast radius if misused by an AI agent.
From the tool's definition The tool is explicitly described as 'read-only' and 'resolves the newest indexed XDaLa session from the Explorer database.' It retrieves session data without modification or side effects.
Attacks that exploit this kind of access
Use this when the user asks for the latest XDaLa session but does not provide owner and sessionId. This read-only tool resolves the newest indexed XDaLa session from the Explorer database and can optionally include final receipt payload data. 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 find_latest_xdala_session: 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.
find_latest_xdala_session 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 find_latest_xdala_session 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 find_latest_xdala_session. 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.
find_latest_xdala_session 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 →