stx_get_contract_events
Get event history for a smart contract.
This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/stx-get-contract-events.md
What stx_get_contract_events does on Bitcoin wallet MCP server
AI agents call stx_get_contract_events 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_get_contract_events is rated Low
This tool queries and retrieves event history from a smart contract, performing a passive data lookup operation. There is no creation, modification, deletion, or execution of code/commands. The action is purely informational and carries no ability to alter state or commit financial obligations. Even in the context of a wallet server, this is a non-destructive read operation.
From the tool's definition Tool name 'stx_get_contract_events' and description 'Get event history for a smart contract' indicate read-only retrieval of historical data with no mutation or side effects.
Attacks that exploit this kind of access
The rule that runs stx_get_contract_events 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_get_contract_events, this is the rule to start with:
stx_get_contract_events 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_get_contract_events call is checked against it from then on.
Questions about stx_get_contract_events
Get event history for a smart contract. 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_contract_events: 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_contract_events 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_contract_events 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_contract_events. 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_contract_events 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