stx_mempool_get_stats
Get Stacks mempool statistics including transaction counts by type,
This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/stx-mempool-get-stats.md
What stx_mempool_get_stats does on Bitcoin wallet MCP server
AI agents call stx_mempool_get_stats 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.
Why stx_mempool_get_stats is rated Low
This tool retrieves and reports statistics about pending transactions in the Stacks mempool. It performs no write, execute, or financial operations—it only reads and returns observational data about network state. Even in a wallet context where financial operations are possible, this specific tool has no capability to move funds, execute code, or modify any blockchain state.
From the tool's definition Tool name 'stx_mempool_get_stats' and description 'Get Stacks mempool statistics including transaction counts by type' indicate a query-only operation that retrieves mempool data without modifying state or initiating transactions.
Attacks that exploit this kind of access
The rule that runs stx_mempool_get_stats 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 stx_mempool_get_stats, this is the rule to start with:
stx_mempool_get_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every stx_mempool_get_stats call is checked against it from then on.
Questions about stx_mempool_get_stats
Get Stacks mempool statistics including transaction counts by type,. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_mempool_get_stats: 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.
stx_mempool_get_stats 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 stx_mempool_get_stats 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 stx_mempool_get_stats. 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.
stx_mempool_get_stats 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.
More on Bitcoin wallet MCP server, and thousands of servers like it.
This server
Across the catalogue