Read-only list of sessions associated with an XRC-729 OSTC id/hash.
AI agents call list_xrc_process_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 information about blockchain sessions without any ability to modify, delete, or execute actions. The 'read-only' designation and the action of listing/querying data firmly places it in the Read category. The severity is low because listing sessions poses minimal risk—it reveals information but cannot cause side effects or irreversible changes.
From the tool's definition The tool is described as 'Read-only list of sessions' which explicitly indicates retrieval without modification. It queries sessions associated with an identifier, performing a passive data lookup.
Attacks that exploit this kind of access
Read-only list of sessions associated with an XRC-729 OSTC id/hash. 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 list_xrc_process_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.
list_xrc_process_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 list_xrc_process_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 list_xrc_process_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.
list_xrc_process_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 →