Measure revenue concentration across the user's ACCOUNTS: top-1 / top-5 / top-10 ARR share, a Herfindahl (HHI) concentration index, whale dependency, and at-risk ARR (low-health accounts' share). Returns the metrics, the largest accounts, and plain-English risk callouts (e.g. 'top 5 = 48% of ARR'...
AI agents call analyze_concentration_risk to retrieve information from StackSwap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
accounts | array | Yes | Accounts as loose records. Recognized fields (with aliases): arr/mrr/contractValue, health/healthScore, name/company. |
lowHealthThreshold | number | — | Health score (0-100) below which an account counts as at-risk (default 60). |
Parameters from the server's own tool schema.
This tool retrieves and analyzes existing account data to compute concentration metrics (HHI, ARR share, health scores). It produces insights and reports without modifying any underlying data. It is a pure read operation with no side effects, no code execution, and no destructive or financial impact. The low severity reflects that misuse (e.g., an agent requesting concentration analysis) poses minimal risk.
From the tool's definition Tool description states it "Measure[s] revenue concentration", "Returns the metrics", and "Operates only on the user's own book". The verb phrases are analytical: 'measure', 'returns', 'analyze'. No create, modify, delete, or execute operations are performed.
Attacks that exploit this kind of access
Measure revenue concentration across the user's ACCOUNTS: top-1 / top-5 / top-10 ARR share, a Herfindahl (HHI) concentration index, whale dependency, and at-risk ARR (low-health accounts' share). Returns the metrics, the largest accounts, and plain-English risk callouts (e.g. 'top 5 = 48% of ARR', 'largest account = 22% — whale risk'). Accepts loosely-typed account records (arr/mrr, health/healthScore normalized); lowHealthThreshold (default 60) sets the at-risk cutoff. Operates only on the user's own book. Use when the user asks 'how concentrated is my revenue', 'what's my whale risk', or pastes accounts with ARR. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
analyze_concentration_risk accepts 2 parameters: accounts, lowHealthThreshold. Required: accounts. The full parameter table on this page comes from the server's own tool schema.
Register the StackSwap MCP server in PolicyLayer and add a rule for analyze_concentration_risk: 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 StackSwap. Nothing to install.
analyze_concentration_risk 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 analyze_concentration_risk 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 analyze_concentration_risk. 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.
analyze_concentration_risk is provided by the StackSwap MCP server (StonesofCreation/stackswap-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 →