get_recent_transactions

What get_recent_transactions does on Indie Metrics

AI agents call get_recent_transactions to retrieve information from Indie Metrics 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 queries historical transaction data (charges, payments, amounts, status, customer email) for visibility and reporting purposes. It retrieves existing financial information without creating, modifying, deleting, or executing operations. The fact that it accesses financial data does not elevate it to the Financial category—it must move money or commit financial obligations to qualify.

From the tool's definition Tool name 'get_recent_transactions' and description 'List recent charges and payments' indicate retrieval/query of transaction data without modification. The word 'List' explicitly denotes a read operation.

The rule that runs get_recent_transactions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Indie Metrics, 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