getWalletHistory

THE RISK

Low Risk

Why getWalletHistory needs a policy

This tool retrieves and queries past transaction records from a blockchain without creating, modifying, deleting, or executing any operations. It is a passive read operation with no irreversible consequences or ability to move funds. The blast radius is minimal since the tool only exposes historical data already recorded on-chain.

From the tool's definition Tool name 'getWalletHistory' and description 'Get transaction history for a wallet on a specific blockchain network' indicate retrieval of historical data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access getWalletHistory gives an agent:

POLICY

How to control getWalletHistory

PolicyLayer is an MCP gateway — it sits between your AI agents and Boosty MCP DeFi Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for getWalletHistory:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getWalletHistory": {}
  }
}

getWalletHistory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Boosty MCP DeFi Platform — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Boosty MCP DeFi Platform tools

Financial execute_swap Execute a token swap via Jupiter aggregator Financial buy_token Buy a token using SOL Financial consolidate_funds Consolidate SOL from multiple wallets into a single target wallet Financial distribute_funds Distribute SOL from a source wallet to multiple target wallets Financial sell_token Sell a token for SOL Destructive delete_wallet Delete a wallet (must have zero balance) Execute execute_batch_swaps Execute multiple swaps in sequence or parallel Execute start_bot Start a bot

All 80 Boosty MCP DeFi Platform tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getWalletHistory

What does the getWalletHistory tool do? +

Get transaction history for a wallet on a specific blockchain network. It is categorised as a Read tool in the Boosty MCP DeFi Platform MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getWalletHistory? +

Register the Boosty MCP DeFi Platform MCP server in PolicyLayer and add a rule for getWalletHistory: 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 Boosty MCP DeFi Platform. Nothing to install.

What risk level is getWalletHistory? +

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

Can I rate-limit getWalletHistory? +

Yes. Add a rate_limit block to the getWalletHistory 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 getWalletHistory completely? +

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

getWalletHistory is provided by the Boosty MCP DeFi Platform MCP server (nirholas/boosty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Boosty MCP DeFi Platform tool call.

Start from Boosty MCP DeFi Platform, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →