get_transaction_stats

Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.

Server XGR MCP Gateway xgr-network/xgr-mcp
Category Read
Risk class Low
Parameters 00 required

What get_transaction_stats does on XGR MCP Gateway

AI agents call get_transaction_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.

Why get_transaction_stats needs a policy

This tool purely queries and retrieves pre-computed transaction statistics from a blockchain explorer index. It has no side effects, cannot modify state, execute code, or trigger on-chain actions. The read-only designation and statistical query nature confirm it is a safe Read operation with minimal blast radius if misused by an agent.

From the tool's definition Tool name contains 'get_', description explicitly states 'Read-only', and retrieves 'chain transaction statistics' from an index with optional filtering parameters. No modification, execution, deletion, or financial impact capability.

Questions about get_transaction_stats

What does the get_transaction_stats tool do? +

Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_transaction_stats? +

Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_transaction_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.

What risk level is get_transaction_stats? +

get_transaction_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_transaction_stats? +

Yes. Add a rate_limit block to the get_transaction_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.

How do I block get_transaction_stats completely? +

Set action: deny in the PolicyLayer policy for get_transaction_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.

What MCP server provides get_transaction_stats? +

get_transaction_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.