T08 · Insecure Dependencies
- Location
ai_and_mcp.md:8- Finding
Unpinned Remote MCP Server and Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This QuickBooks skill is mostly coherent documentation, but it includes under-scoped guidance for AI-driven payment actions and an unpinned third-party MCP installation path.
Review carefully before installing. Use sandbox or read-only QuickBooks scopes first, protect refresh tokens, pin and audit any MCP server dependency before running npm install, and require explicit human approval plus deterministic checks for any payment, charge, refund, bill, journal, or account-changing operation.
ai_and_mcp.md:8Unpinned Remote MCP Server and Dependency Installation
ai_and_mcp.md:52LLM Decision Directly Authorizes a Consequential Payment Action
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
description: OAuth 2.0 Client Secret from the Intuit Developer Portal.
- name: QUICKBOOKS_REFRESH_TOKEN
required: true
description: Long-lived OAuth 2.0 refresh token (valid for 100 days). Used to obtain new access tokens.
- name: QUICKBOOKS_REALM_ID
required: true
description: The QuickBooks Online company ID (realmId) obtained after the user completes the OAuth authorization flow.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
### Step 3: Refreshing Tokens
Access tokens expire after **60 minutes**. Refresh tokens expire after **100 days**.
* **Endpoint:** `https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer`
* **Body:**
```
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| **`2030`** | `400 Bad Request` | Stale `SyncToken` during update. | Fetch the latest version of the entity, merge changes, and retry. |
| **`3100`** | `400 Bad Request` | Duplicate `DocNumber`. | Enable `allowduplicatedocnum` query parameter or let system auto-generate. |
| **`3200`** | `400 Bad Request` | Transaction is locked / reconciled. | Do not allow edits via API; prompt user to unlock inside QuickBooks UI. |
| **`100`** | `401 Unauthorized` | Invalid or expired Access Token. | Execute OAuth token refresh flow and retry the request. |
| **`429`** | `429 Too Many Requests`| API rate limit exceeded (100 req/min). | Implement exponential backoff with jitter. |
### Exponential Backoff Implementation (Python)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| Operation | Endpoint |
| :--- | :--- |
| Tokenize card | `POST https://api.intuit.com/quickbooks/v4/payments/tokens` |
| Create charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges` |
| Refund charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges/<id>/refunds` |
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| Operation | Endpoint |
| :--- | :--- |
| Tokenize card | `POST https://api.intuit.com/quickbooks/v4/payments/tokens` |
| Create charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges` |
| Refund charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges/<id>/refunds` |
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
| Operation | Endpoint |
| :--- | :--- |
| Tokenize card | `POST https://api.intuit.com/quickbooks/v4/payments/tokens` |
| Create charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges` |
| Refund charge | `POST https://api.intuit.com/quickbooks/v4/payments/charges/<id>/refunds` |
The document presents an AI-driven workflow that can culminate in a Pay Bill action based on an LLM-mediated matching decision, but it does not include any guardrails such as human approval, confidence thresholds, transaction limits, or warnings about irreversible financial actions. In the context of accounting automation, this creates a real risk of unauthorized, mistaken, or manipulated payments if an agent acts on ambiguous data, webhook spoofing, or model error.
The guidance recommends backslash-escaping single quotes before interpolating user input into an IDS query string, which is not a reliably safe escaping strategy for SQL-like languages and may not match QuickBooks IDS parsing rules. This can lead developers to build queries by concatenation, allowing malformed queries, filter bypass, or injection-like manipulation of returned accounting data.
This markdown file describes the Change Data Capture endpoint and shows how to query changed Customer and Invoice records, but it does not warn that the operation may expose or process large amounts of potentially sensitive accounting data. Under the markdown-specific warning criterion, data-affecting or privacy-relevant behaviors should be disclosed to the user.