Get transaction history for a wallet. Retrieves recent transactions for the specified wallet from the RustChain network. Args: wallet_id: The wallet ID to get history for limit: Maximum number of transactions to return (default: 20, max: 100) Returns list of transactions with type, amount, timest...
AI agents call wallet_history to retrieve information from RustChain + BoTTube MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
wallet_history is a read-only operation that queries and returns transaction history. It has no side effects—it does not create, modify, delete, or execute any operations. The tool only accesses existing blockchain data for viewing purposes. While it reveals financial transaction details (which could inform later financial actions by an agent), the tool itself performs no financial transaction.
From the tool's definition Tool 'retrieves recent transactions for the specified wallet from the RustChain network' and 'Returns list of transactions with type, amount, timestamp, and counterparty.' The description explicitly states it retrieves/queries data without modification.
Documented attack patterns abuse exactly the kind of access wallet_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RustChain + BoTTube MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wallet_history:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_history": {}
}
}wallet_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get transaction history for a wallet. Retrieves recent transactions for the specified wallet from the RustChain network. Args: wallet_id: The wallet ID to get history for limit: Maximum number of transactions to return (default: 20, max: 100) Returns list of transactions with type, amount, timestamp, and counterparty. It is categorised as a Read tool in the RustChain + BoTTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RustChain + BoTTube MCP Server MCP server in PolicyLayer and add a rule for wallet_history: 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 RustChain + BoTTube MCP Server. Nothing to install.
wallet_history 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_history 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_history. 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_history is provided by the RustChain + BoTTube MCP Server MCP server (scottcjn/rustchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 39 RustChain + BoTTube MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
39 RustChain + BoTTube MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.