# get_recent_transactions

List recent charges and payments with amount, status, customer email,

Agent View of the PolicyLayer registry record for `get_recent_transactions`. HTML page: https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-recent-transactions

## Facts

- Tool: `get_recent_transactions`
- Server: Indie Metrics (`marccherggi/indie-metrics-mcp`) — https://policylayer.com/tools/marccherggi-indie-metrics-mcp.md
- Homepage: https://github.com/MARCCHERGGI/indie-metrics-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_recent_transactions",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Indie Metrics:

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

## Other tools on Indie Metrics (6)

- `get_customer_metrics` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-customer-metrics.md
- `get_product_performance` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-product-performance.md
- `get_refund_analysis` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-refund-analysis.md
- `get_revenue_forecast` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-revenue-forecast.md
- `get_revenue_summary` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-revenue-summary.md
- `get_subscription_health` — Read — https://policylayer.com/tools/marccherggi-indie-metrics-mcp/get-subscription-health.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=marccherggi-indie-metrics-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/marccherggi-indie-metrics-mcp