Compare two periods of journal-entry data (QBO or Xero — source auto-detected from headers) and flag accounts whose movement deviates materially between periods. Aggregates lines per account into a net total for each period, then surfaces accounts where the period-over-period change crosses a mat...
AI agents call analyze_journal_variance to retrieve information from HelloBooks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
periodACsv | string | Yes | Raw CSV text of the EARLIER period's journal-entry export (QBO Journal Entries or Xero Manual Journals). Source is auto-detected from the headers. |
periodBCsv | string | Yes | Raw CSV text of the LATER period's journal-entry export. Source is auto-detected from the headers (must match periodACsv). |
periodALabel | string | — | Optional human label for the earlier period — e.g. "Q1 FY2024". Used in flag messages. |
periodBLabel | string | — | Optional human label for the later period — e.g. "Q2 FY2024". |
Parameters from the server's own tool schema.
analyze_journal_variance performs statistical comparison and anomaly detection on financial data without altering, deleting, or executing transactions. It ingests two period snapshots and produces analysis output. While the server context is financial, this specific tool does not move money, commit obligations, or trigger irreversible changes—it only reads and reports.
From the tool's definition Tool compares and analyzes journal-entry data across periods, flags accounts with material variance, and surfaces anomalies. No modification, deletion, or execution of external operations—purely data retrieval and analysis (analyze_*, compare_*).
Attacks that exploit this kind of access
Compare two periods of journal-entry data (QBO or Xero — source auto-detected from headers) and flag accounts whose movement deviates materially between periods. Aggregates lines per account into a net total for each period, then surfaces accounts where the period-over-period change crosses a materiality threshold (≥5% relative AND ≥$100 absolute; severity high at ≥50%, medium at ≥20%, low at ≥5%). Inputs are two CSV exports — periodACsv (earlier period) and periodBCsv (later period). Optional periodALabel / periodBLabel for human-readable flag messages (e.g. "Q1 FY2024" vs "Q2 FY2024"). Max 5,000 rows per period; max 5 MB each. Use this when a user pastes two periods and asks "what changed?", "show me variances", "what jumped period-over-period". Returns a flag list ordered by largest delta, a roll-up, and a shareable URL. Both periods must be the same source — mixing QBO + Xero in one call returns an error. It is categorised as a Read tool in the HelloBooks AI MCP Server MCP Server, which means it retrieves data without modifying state.
analyze_journal_variance accepts 4 parameters: periodACsv, periodBCsv, periodALabel, periodBLabel. Required: periodACsv, periodBCsv. The full parameter table on this page comes from the server's own tool schema.
Register the HelloBooks AI MCP Server MCP server in PolicyLayer and add a rule for analyze_journal_variance: 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 HelloBooks AI MCP Server. Nothing to install.
analyze_journal_variance 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_journal_variance 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_journal_variance. 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_journal_variance is provided by the HelloBooks AI MCP Server MCP server (Meru-Fin-Tech/HelloBooks-MCP-Public). 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 →