Use this when the user asks which payload fields/keys occurred, how often payload fields appeared, or which payload fields were empty/non-empty. For “last 14 days”, pass windowHours=336.
AI agents call get_xdala_payload_key_stats 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 is a data retrieval and analytics tool that queries historical blockchain payload statistics. It has no side effects, cannot modify state, and presents minimal risk if an AI agent invokes it with any parameters. The worst case is retrieving irrelevant statistics, which causes no harm.
From the tool's definition Tool retrieves statistics about payload fields/keys (occurrence counts, empty/non-empty status). Description indicates querying and analysis only: 'which payload fields occurred, how often payload fields appeared, which payload fields were empty/non-empty'.
Attacks that exploit this kind of access
Use this when the user asks which payload fields/keys occurred, how often payload fields appeared, or which payload fields were empty/non-empty. For “last 14 days”, pass windowHours=336. 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_payload_key_stats: 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_payload_key_stats 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_payload_key_stats 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_payload_key_stats. 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_payload_key_stats 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 →