egress_log
Show recent ComplyEaze Bridge tool-call receipts from its local log—tool, time, company, counts, fingerprints, no book figures—so users and reviewers can see which calls ran, on which company, when.
Instructions
Everything the assistant reads from Tally through ComplyEaze Bridge in this chat, amounts included, is sent to the AI provider; redaction can only shorten party and ledger names and bank account numbers or drop narrations, and does not hide amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details or references, or the last four digits of a bank statement's account number (account_last4); under mask_parties a name written inside a narration or reference stays as it is. Never tell the user that no data has left their computer. Shows the receipts ComplyEaze Bridge keeps of its own tool calls, read from its local log file on this computer: tool, time, company, counts and fingerprints, no figures or book content (bounded to the most recent receipts). It does not show what the AI provider received. Use it when the user asks what ComplyEaze Bridge has done, or to show a reviewer which calls ran, on which company and when. Reading the log changes nothing in it; this call's own receipt lines are added after the read, like every call's. Each call appends metadata-only receipt lines (tool, company, counts, request and response fingerprints; no book content) to ComplyEaze Bridge's local log on this computer; it writes nothing to Tally.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many of the most recent receipt lines to return (each completed call writes two): default 20, at most 256 (or the configured row limit, BRIDGE_AGENT_MAX_ROWS, if lower, which can cap the default too), and fewer when the newest receipt lines do not fit in the log read's size bound. |