swap_get_history

Get swap transaction history from on-chain activity.

SERVERBitcoin wallet MCP server SOURCEmarkmhendrickson/mcp-server-bitcoin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/swap-get-history.md

WHAT IT DOES

What swap_get_history does on Bitcoin wallet MCP server

AI agents call swap_get_history to retrieve information from Bitcoin wallet MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why swap_get_history is rated Low

This tool retrieves historical transaction data from blockchain records. It performs a read-only query operation with no side effects, no code execution, and no financial transactions initiated. The tool cannot modify data, delete records, or execute operations—it only fetches and returns existing swap history information.

From the tool's definition Tool name 'swap_get_history' and description 'Get swap transaction history from on-chain activity' indicate data retrieval with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swap_get_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For swap_get_history, this is the rule to start with:

swap_get_history Allowed

swap_get_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every swap_get_history call is checked against it from then on.

FAQ

Questions about swap_get_history

What does the swap_get_history tool do? +

Get swap transaction history from on-chain activity. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on swap_get_history? +

Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for swap_get_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 Bitcoin wallet MCP server. Nothing to install.

What risk level is swap_get_history? +

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

Can I rate-limit swap_get_history? +

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

How do I block swap_get_history completely? +

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

What MCP server provides swap_get_history? +

swap_get_history is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bitcoin wallet MCP server, and thousands of servers like it.

This server

All 93 Bitcoin wallet MCP server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →