Get transaction history for a wallet address. Returns up to 100 transactions
AI agents call wallet_transactions to retrieve information from Kxcoscan AI Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical blockchain data and returns information without creating, modifying, deleting, or executing any operations. It has no side effects on blockchain state or external systems. The read-only nature of transaction history queries and the bounded return size (100 transactions) further confirm low severity.
From the tool's definition Tool retrieves transaction history for a wallet address with no modification capability. Description explicitly states 'Get transaction history' and 'Returns up to 100 transactions', indicating a data retrieval operation with a bounded result set.
Attacks that exploit this kind of access
Get transaction history for a wallet address. Returns up to 100 transactions. It is categorised as a Read tool in the Kxcoscan AI Tools MCP Server, which means it retrieves data without modifying state.
Register the Kxcoscan AI Tools MCP server in PolicyLayer and add a rule for wallet_transactions: 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 Kxcoscan AI Tools. Nothing to install.
wallet_transactions 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 wallet_transactions 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 wallet_transactions. 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.
wallet_transactions is provided by the Kxcoscan AI Tools MCP server (keralpatel/kxcoscan-mcp-server). 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 →