This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/quickbooks-customers.md
What quickbooks_customers does on UnClick
AI agents call quickbooks_customers to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
where | string | — | SQL-style WHERE clause (e.g. Active = true) |
offset | number | — | |
sandbox | boolean | — | |
realm_id | string | Yes | QuickBooks company realm ID |
access_token | string | Yes | QuickBooks OAuth2 access token |
Parameters from the server's own tool schema.
Why quickbooks_customers is rated Low
This tool retrieves or queries customer data from QuickBooks Online without modifying, deleting, or executing operations. It is a straightforward read operation with no side effects. Severity is low because querying customer lists, while potentially exposing business information, does not immediately compromise financial transactions or enable destructive actions.
From the tool's definition Tool name is 'quickbooks_customers' and description states 'Query QuickBooks Online customers' — both indicate data retrieval with the verb 'query' and no mention of creation, modification, or deletion.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs quickbooks_customers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For quickbooks_customers, this is the rule to start with:
quickbooks_customers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every quickbooks_customers call is checked against it from then on.
Questions about quickbooks_customers
Query QuickBooks Online customers. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
quickbooks_customers accepts 6 parameters: limit, where, offset, sandbox, realm_id, access_token. Required: realm_id, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for quickbooks_customers: 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 UnClick. Nothing to install.
quickbooks_customers 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 quickbooks_customers 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 quickbooks_customers. 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.
quickbooks_customers is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue