get_customer_metrics

Get customer analytics including total customers, new customers in period,

SERVERIndie Metrics SOURCEmarccherggi/indie-metrics-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/marccherggi-indie-metrics-mcp/get-customer-metrics.md

WHAT IT DOES

What get_customer_metrics does on Indie Metrics

AI agents call get_customer_metrics 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.

RISK

Why get_customer_metrics is rated Low

This tool retrieves and queries customer analytics from Stripe—a passive read operation with no side effects. It does not create, modify, delete, or execute operations. While the data is business-sensitive, the low severity reflects that unauthorized access to metrics is less critical than write/execute/destructive capabilities.

From the tool's definition Tool name 'get_customer_metrics' and description indicating it retrieves analytics data ('Get customer analytics including total customers, new customers in period').

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_customer_metrics Allowed

get_customer_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Indie Metrics, apply this rule, and every get_customer_metrics call is checked against it from then on.

FAQ

Questions about get_customer_metrics

What does the get_customer_metrics tool do? +

Get customer analytics including total customers, new customers in period,. 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_customer_metrics? +

Register the Indie Metrics MCP server in PolicyLayer and add a rule for get_customer_metrics: 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_customer_metrics? +

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

Can I rate-limit get_customer_metrics? +

Yes. Add a rate_limit block to the get_customer_metrics 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_customer_metrics completely? +

Set action: deny in the PolicyLayer policy for get_customer_metrics. 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_customer_metrics? +

get_customer_metrics 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.

KEEP EXPLORING

More on Indie Metrics, and thousands of servers like it.

This server

All 7 Indie Metrics tools →

Across the catalogue

aiva_get_customer on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →