Use this when the user asks for the payload of the latest XDaLa session. This read-only tool resolves the latest indexed session without requiring owner plus sessionId, then returns payload, apiSaves, contractSaves and extras from the final receipt.
AI agents call get_latest_session_payload 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 queries blockchain session data and returns information about the latest XDaLa session. It has no side effects, does not modify state, and does not execute code or trigger external operations. It is a straightforward read operation with minimal blast radius if misused—an agent could only retrieve existing data.
From the tool's definition Tool description explicitly states 'read-only tool' and performs data retrieval operations: 'returns payload, apiSaves, contractSaves and extras from the final receipt.' No modifications, deletions, or external operations are performed.
Attacks that exploit this kind of access
Use this when the user asks for the payload of the latest XDaLa session. This read-only tool resolves the latest indexed session without requiring owner plus sessionId, then returns payload, apiSaves, contractSaves and extras from the final receipt. 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_latest_session_payload: 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_latest_session_payload 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_latest_session_payload 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_latest_session_payload. 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_latest_session_payload 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 →