Get transaction history (native transfers, ERC-20 transfers, NFT activity) for a specific account on a specific blockchain. Supports both Agent Wallet (EOA) and Smart Accounts on EVM and Solana chains. Both account address and chain must be specified - activity cannot be mixed across different ch...
Single-target operation
Part of the Finance District MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call getAccountActivity to retrieve information from Finance District without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though getAccountActivity only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
getAccountActivity:
rules:
- action: allowSee the full Finance District policy for all 16 tools.
Get transaction history (native transfers, ERC-20 transfers, NFT activity) for a specific account on a specific blockchain. Supports both Agent Wallet (EOA) and Smart Accounts on EVM and Solana chains. Both account address and chain must be specified - activity cannot be mixed across different chains or accounts.. It is categorised as a Read tool in the Finance District MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for getAccountActivity. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Finance District MCP server.
getAccountActivity 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 getAccountActivity rule in your Intercept 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 Intercept policy for getAccountActivity. 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.
getAccountActivity is provided by the Finance District MCP server (finance-district/agent-wallet). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept