Authenticate with QuickBooks using OAuth (local credential mode only). Step 1: Call with no arguments to get the authorization URL. Step 2: After authorizing in browser, call with authorization_code and realm_id from the callback URL. This tool only works when QBO_CREDENTIAL_MODE is 'local' (the ...
Part of the Quickbooks MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call qbo_authenticate to retrieve information from Quickbooks without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though qbo_authenticate only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
qbo_authenticate:
rules:
- action: allow See the full Quickbooks policy for all 34 tools.
Authenticate with QuickBooks using OAuth (local credential mode only). Step 1: Call with no arguments to get the authorization URL. Step 2: After authorizing in browser, call with authorization_code and realm_id from the callback URL. This tool only works when QBO_CREDENTIAL_MODE is 'local' (the default).. It is categorised as a Read tool in the Quickbooks MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for qbo_authenticate. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Quickbooks MCP server.
qbo_authenticate 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_authenticate rule in your Intercept 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 Intercept policy for qbo_authenticate. 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_authenticate is provided by the Quickbooks MCP server (quickbooks-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept