get_transaction_events

What get_transaction_events does on Stacks AI MCP Server

AI agents call get_transaction_events to retrieve information from Stacks AI 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 get_transaction_events is rated Low

This tool retrieves historical blockchain event data associated with a specific transaction. It performs a read-only query operation with filtering capabilities but produces no side effects, data modifications, financial movements, or code execution. The blast radius of misuse is minimal—an agent could retrieve information about transactions, but cannot alter state, execute operations, or move funds.

From the tool's definition Tool name 'get_transaction_events' and description 'Get events for a specific transaction with detailed filtering' indicate retrieval and querying of blockchain transaction data with no modification or execution capability.

The rule that runs get_transaction_events safely

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

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

Questions about get_transaction_events