Get events for a specific transaction with detailed filtering
AI agents call get_transaction_events to retrieve information from Stacks AI 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 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.
Attacks that exploit this kind of access
Get events for a specific transaction with detailed filtering. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_transaction_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 Stacks AI MCP Server. Nothing to install.
get_transaction_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 get_transaction_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 get_transaction_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.
get_transaction_events is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →