get_stx_transfer_events
Get STX transfer, mint, and burn events
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-stx-transfer-events.md
What get_stx_transfer_events does on Stacks AI MCP Server
AI agents call get_stx_transfer_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_stx_transfer_events is rated Low
This tool queries and retrieves past blockchain events (transfers, mints, burns) without creating, modifying, executing, or deleting any data. It is a read-only operation that returns information about transactions that have already occurred on the Stacks blockchain. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'get_stx_transfer_events' and description 'Get STX transfer, mint, and burn events' indicate retrieval of historical blockchain events with no modification or execution of operations.
Attacks that exploit this kind of access
The rule that runs get_stx_transfer_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_stx_transfer_events, this is the rule to start with:
get_stx_transfer_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 Stacks AI MCP Server, apply this rule, and every get_stx_transfer_events call is checked against it from then on.
Questions about get_stx_transfer_events
Get STX transfer, mint, and burn events. 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_stx_transfer_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_stx_transfer_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_stx_transfer_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_stx_transfer_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_stx_transfer_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.
More on Stacks AI MCP Server, and thousands of servers like it.
This server
Across the catalogue