Low Risk

query_account_transactions

Query all transactions affecting a specific account. Searches across JournalEntry, Purchase, Deposit, SalesReceipt, Bill, Invoice, and Payment. Returns consolidated list with date, type, amount (debit/credit), and description. Useful for investigating account balance discrepancies.

Single-target operation

Part of the Quickbooks MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call query_account_transactions 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 query_account_transactions 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.

io-github-nyxtoolsdev-quickbooks-mcp-server.yaml
tools:
  query_account_transactions:
    rules:
      - action: allow

See the full Quickbooks policy for all 34 tools.

Tool Name query_account_transactions
Category Read
Risk Level Low

View all 34 tools →

What does the query_account_transactions tool do? +

Query all transactions affecting a specific account. Searches across JournalEntry, Purchase, Deposit, SalesReceipt, Bill, Invoice, and Payment. Returns consolidated list with date, type, amount (debit/credit), and description. Useful for investigating account balance discrepancies.. It is categorised as a Read tool in the Quickbooks MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_account_transactions? +

Add a rule in your Intercept YAML policy under the tools section for query_account_transactions. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Quickbooks MCP server.

What risk level is query_account_transactions? +

query_account_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_account_transactions? +

Yes. Add a rate_limit block to the query_account_transactions 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.

How do I block query_account_transactions completely? +

Set action: deny in the Intercept policy for query_account_transactions. 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.

What MCP server provides query_account_transactions? +

query_account_transactions 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.

Enforce policies on Quickbooks

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.