Scan for customer Payments with money not applied to any invoice (header UnappliedAmt > 0 — correctly catches fully-unapplied payments, which QBO returns with an empty Line array). Pulls ALL Payments page-by-page because UnappliedAmt is not SOQL-filterable, so it can take a while on large realms;...
AI agents call qbo_scan_unapplied_payments to retrieve information from Kaizen Qbo 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 financial data (unapplied customer payments) from QuickBooks Online without creating, modifying, deleting, or executing any transactions. While it accesses sensitive financial information, the read-only nature and lack of side effects place it in the Read category.
From the tool's definition Tool description explicitly states 'Read-only' and the function scans for unapplied payments without modifying data. It 'Pulls ALL Payments page-by-page' and 'Returns payment-level items' for analysis purposes only.
Attacks that exploit this kind of access
Scan for customer Payments with money not applied to any invoice (header UnappliedAmt > 0 — correctly catches fully-unapplied payments, which QBO returns with an empty Line array). Pulls ALL Payments page-by-page because UnappliedAmt is not SOQL-filterable, so it can take a while on large realms; the result carries truncated:true if the page cap was hit. Returns payment-level items with QBO deep links, a per-customer rollup, totalAmount, and severity (critical when total > $25,000). Read-only. Optional start/end bound TxnDate — omit to scan all time (recommended: unapplied is a point-in-time condition and old payments matter). It is categorised as a Read tool in the Kaizen Qbo MCP Server, which means it retrieves data without modifying state.
Register the Kaizen Qbo MCP server in PolicyLayer and add a rule for qbo_scan_unapplied_payments: 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 Kaizen Qbo. Nothing to install.
qbo_scan_unapplied_payments 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 qbo_scan_unapplied_payments 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 qbo_scan_unapplied_payments. 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.
qbo_scan_unapplied_payments is provided by the Kaizen Qbo MCP server (kaizen-qbo-mcp-server). 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 →