Get a customer by Id from QuickBooks Online.
AI agents call get_customer 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 customer data from QuickBooks Online without modifying, deleting, or executing any operations. It is a straightforward read operation that returns existing data. The blast radius of misuse is minimal—an attacker could enumerate or exfiltrate customer records but cannot alter financial state or trigger transactions.
From the tool's definition Tool name is 'get_customer' and description states 'Get a customer by Id from QuickBooks Online' — the verb 'Get' and the retrieval-only semantics indicate a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_customer 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 get_customer:
{
"version": "1",
"default": "deny",
"tools": {
"get_customer": {}
}
} get_customer 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.
Get a customer by Id from QuickBooks Online. 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 get_customer: 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.
get_customer 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 get_customer 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 get_customer. 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.
get_customer 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.