What it can see
Only the summary figures a user asks for, within their existing Harmonize permissions, reach the AI assistant. Harmonize MCP returns governed metric totals, trends, breakdowns and comparisons, not transaction-level records. These cover sales and transaction volumes, refunds, fees, interchange, effective rates, approval and decline rates, and dispute figures.
Figures can be broken down by merchant, processor, card brand or type, channel, BIN, MID, location and period, as well as approved merchant and MID attributes, subscription identifiers and client-configured labels where populated.
Harmonize MCP uses the same governed data as Harmonize Analytics, and most metrics are available in both. A few Harmonize Analytics metrics aren't available in the MCP, and the MCP has a few extra metrics it uses to calculate rates. The Data Dictionary shows which metrics are available in Harmonize MCP.
What it can't see
-
Individual transactions, refunds or disputes
-
Card numbers (PAN), full or masked. The closest it gets is a 6- to 8-digit BIN.
-
CVVs
-
Cardholder names, contact details or payer identities
-
Other clients' data
These fields aren't in the catalog, so an AI assistant can't request them. Requests for transaction-level records or card numbers are declined.
How queries are built
Harmonize generates each query on its own servers from the governed metric catalog and a validated list of allowed columns, with access limited to your organization. Your AI assistant can't submit its own SQL or select other columns through these tools.