get_recent_transactions

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

Server Indie Metrics marccherggi/indie-metrics-mcp
Category Read
Risk class Low
Parameters 00 required

What get_recent_transactions does on Indie Metrics

AI agents call get_recent_transactions to retrieve information from Indie Metrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_recent_transactions needs a policy

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.

Questions about get_recent_transactions

What does the get_recent_transactions tool do? +

List recent charges and payments with amount, status, customer email,. It is categorised as a Read tool in the Indie Metrics MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_transactions? +

Register the Indie Metrics MCP server in PolicyLayer and add a rule for get_recent_transactions: 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 Indie Metrics. Nothing to install.

What risk level is get_recent_transactions? +

get_recent_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_transactions? +

Yes. Add a rate_limit block to the get_recent_transactions 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.

How do I block get_recent_transactions completely? +

Set action: deny in the PolicyLayer policy for get_recent_transactions. 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.

What MCP server provides get_recent_transactions? +

get_recent_transactions is provided by the Indie Metrics MCP server (marccherggi/indie-metrics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.