Search purchases in QuickBooks Online. Filterable fields: Id, TxnDate, PaymentType, AccountRef, EntityRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime.
AI agents call search_purchases to retrieve information from QuickBooks Online MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries purchase data from QuickBooks without any side effects. It performs a search operation with filtering capabilities only, which is characteristic of Read category tools. The absence of any write, delete, or execute operations and the purely informational nature of the returned data (purchase IDs, dates, amounts, metadata) places this squarely in the Read category with low severity.
From the tool's definition Tool name is 'search_purchases' and description states 'Search purchases in QuickBooks Online' with only read-only filterable fields (Id, TxnDate, PaymentType, etc.). No creation, modification, deletion, or execution verbs present.
Documented attack patterns abuse exactly the kind of access search_purchases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuickBooks Online MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_purchases:
{
"version": "1",
"default": "deny",
"tools": {
"search_purchases": {}
}
} search_purchases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search purchases in QuickBooks Online. Filterable fields: Id, TxnDate, PaymentType, AccountRef, EntityRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime. It is categorised as a Read tool in the QuickBooks Online MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QuickBooks Online MCP Server MCP server in PolicyLayer and add a rule for search_purchases: 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 QuickBooks Online MCP Server. Nothing to install.
search_purchases 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 search_purchases 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 search_purchases. 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.
search_purchases is provided by the QuickBooks Online MCP Server MCP server (librechat-ai/quickbooks-online-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QuickBooks Online MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 QuickBooks Online MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.