client_get
Get complete details of a client including financial summary and recent sessions.
This record as markdown: /tools/com-servicialo-mcp-server/client-get.md
What client_get does on Servicialo
AI agents call client_get to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
clientId | string | Yes | |
includeHistory | boolean | — | |
includeFinancials | boolean | — |
Parameters from the server's own tool schema.
Why client_get is rated Low
This tool retrieves client information including financial summary and session history. While it is a Read operation (no side effects), the inclusion of 'financial summary' elevates severity from low to medium due to potential sensitivity of financial data exposure. The tool does not modify, delete, or execute operations—it only fetches existing data.
From the tool's definition Tool name 'client_get' and description 'Get complete details of a client including financial summary and recent sessions' indicates data retrieval with no modification or deletion.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs client_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For client_get, this is the rule to start with:
client_get 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 Servicialo, apply this rule, and every client_get call is checked against it from then on.
Questions about client_get
Get complete details of a client including financial summary and recent sessions. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
client_get accepts 5 parameters: apiKey, orgSlug, clientId, includeHistory, includeFinancials. Required: orgSlug, clientId. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for client_get: 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 Servicialo. Nothing to install.
client_get 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 client_get 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 client_get. 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.
client_get is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue