Use this when the user asks for active/concurrent XDaLa sessions over time.
AI agents call get_xdala_active_sessions_timeseries 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 historical or real-time metrics about session concurrency without modifying, executing, or deleting any data. It is a pure read operation querying blockchain or application state. The blast radius of misuse is minimal—returning incorrect or excessive data about session counts poses no financial, destructive, or execution risk.
From the tool's definition Tool name and description indicate retrieval of time-series data about active XDaLa sessions ('get_xdala_active_sessions_timeseries').
Attacks that exploit this kind of access
Use this when the user asks for active/concurrent XDaLa sessions over time. 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_xdala_active_sessions_timeseries: 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_xdala_active_sessions_timeseries 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_xdala_active_sessions_timeseries 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_xdala_active_sessions_timeseries. 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_xdala_active_sessions_timeseries 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 →