get_client_history
Complete cross-practice engagement history for a client: all quotes, proposals, contracts, invoices, bookings, projects, and deliveries in a unified timeline.
This record as markdown: /tools/app-businys-mcp-server/get-client-history.md
What get_client_history does on Businys
AI agents call get_client_history to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_client_history is rated Low
This tool queries and returns historical data about a client without modifying, deleting, or executing any operations. It is a straightforward retrieval operation with no side effects. While it may expose sensitive business information (invoices, contracts), the confidentiality risk is a data sensitivity concern separate from the functional classification—the tool itself performs only read operations.
From the tool's definition Tool description uses verb 'get' and explicitly states it 'retrieves' a unified timeline of client records (quotes, proposals, contracts, invoices, bookings, projects, and deliveries). No modification, deletion, or execution is mentioned.
Attacks that exploit this kind of access
The rule that runs get_client_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_client_history, this is the rule to start with:
get_client_history 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 Businys, apply this rule, and every get_client_history call is checked against it from then on.
Questions about get_client_history
Complete cross-practice engagement history for a client: all quotes, proposals, contracts, invoices, bookings, projects, and deliveries in a unified timeline. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_client_history: 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 Businys. Nothing to install.
get_client_history 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_client_history 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_client_history. 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_client_history is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue