Get customer analytics including total customers, new customers in period,
AI agents call get_customer_metrics 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.
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
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.
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.
get_customer_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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 →