This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/quickbooks-payments.md
What quickbooks_payments does on UnClick
AI agents call quickbooks_payments 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 | — | |
offset | number | — | |
sandbox | boolean | — | |
realm_id | string | Yes | |
access_token | string | Yes |
Parameters from the server's own tool schema.
Why quickbooks_payments is rated Low
This tool retrieves or queries financial payment data from QuickBooks Online. While it accesses sensitive financial information (raising severity above 'low' due to exposure of transactional records), it does not move money, create charges, or execute transactions—it only reads existing data.
From the tool's definition Tool name 'quickbooks_payments' combined with description 'Query QuickBooks Online payments' indicates a retrieval operation. The verb 'query' confirms read-only access to payment data without modification or execution capabilities.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs quickbooks_payments 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_payments, this is the rule to start with:
quickbooks_payments 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_payments call is checked against it from then on.
Questions about quickbooks_payments
Query QuickBooks Online payments. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
quickbooks_payments 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_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 UnClick. Nothing to install.
quickbooks_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 quickbooks_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 quickbooks_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.
quickbooks_payments 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