get_recent_transactions

What get_recent_transactions does on Stacks AI MCP Server

AI agents call get_recent_transactions 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_recent_transactions is rated Low

This tool performs a read-only retrieval of existing transaction history. It has no side effects, does not execute trades, does not move funds, and does not modify any data. The blast radius of misuse is minimal—an agent could only view transaction information, which is typically public blockchain data on a Layer 2 system like Stacks.

From the tool's definition Tool name 'get_recent_transactions' and description 'Get list of recent transactions' indicate a query operation that retrieves historical transaction data without modification or execution of new operations.

The rule that runs get_recent_transactions 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_recent_transactions, this is the rule to start with:

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

Questions about get_recent_transactions