Returns all transactions for a given address or script pubkey, allowing insight into when the balance increased, decreased, or remained the same. Mempool data is included by default. This endpoint supports customization to narrow results by time, transaction type, or ordering, enabling tailored h...
AI agents call wallet_satoshi_activity_by_address to retrieve information from Maestro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query tool that retrieves historical transaction data and mempool information from the Bitcoin blockchain. While the data retrieved could theoretically be sensitive (transaction history is public blockchain data), the tool itself performs no state changes, does not execute code, and does not have destructive or financial implications.
From the tool's definition Tool returns transaction history and activity data for a given address ("Returns all transactions for a given address"). It allows querying, filtering, and viewing blockchain data without creating, modifying, or deleting any data.
Documented attack patterns abuse exactly the kind of access wallet_satoshi_activity_by_address gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maestro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wallet_satoshi_activity_by_address:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_satoshi_activity_by_address": {}
}
}wallet_satoshi_activity_by_address 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.
Returns all transactions for a given address or script pubkey, allowing insight into when the balance increased, decreased, or remained the same. Mempool data is included by default. This endpoint supports customization to narrow results by time, transaction type, or ordering, enabling tailored historical views. It is categorised as a Read tool in the Maestro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maestro MCP Server MCP server in PolicyLayer and add a rule for wallet_satoshi_activity_by_address: 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 Maestro MCP Server. Nothing to install.
wallet_satoshi_activity_by_address 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_satoshi_activity_by_address 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_satoshi_activity_by_address. 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_satoshi_activity_by_address is provided by the Maestro MCP Server MCP server (maestro-org/maestro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maestro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
117 Maestro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.