Get recent Stacks blocks with metadata.
AI agents call stx_get_recent_blocks to retrieve information from Bitcoin wallet MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical block information from the Stacks blockchain. It is a passive data query with no capability to modify state, execute code, delete data, or move funds. The operation has minimal blast radius—an AI agent misusing this tool could retrieve block metadata repeatedly but cannot cause harm beyond potential rate-limiting or information disclosure of public blockchain data.
From the tool's definition Tool name 'stx_get_recent_blocks' and description 'Get recent Stacks blocks with metadata' indicate a read-only query operation that retrieves blockchain data without modification, side effects, or financial transactions.
Attacks that exploit this kind of access
Get recent Stacks blocks with metadata. 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_get_recent_blocks: 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_get_recent_blocks 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_get_recent_blocks 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_get_recent_blocks. 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_get_recent_blocks 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →