list_clients
List the subscriber’s clients with their billing profile, optionally filtered by a name/notes search. Answers "who are my clients?"
This record as markdown: /tools/com-getsavitools-savi-tools/list-clients.md
What list_clients does on Savi Tools
AI agents call list_clients to retrieve information from Savi Tools 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 |
|---|---|---|---|
query | string | — | Optional name or notes search. |
Parameters from the server's own tool schema.
Why list_clients is rated Low
This tool retrieves and queries existing client data without any ability to create, modify, delete, or execute operations. The sibling tools (all prefixed with 'get_') and the business context (Savi Tools for invoicing/expense tracking) confirm this is a data retrieval function. The severity is low because listing clients carries minimal risk; the data is already known to the authorized subscriber.
From the tool's definition Tool description states 'List the subscriber's clients' and is designed to answer 'who are my clients?' — a query operation with no modification capability. The optional filtering is a read-only search parameter.
Attacks that exploit this kind of access
The rule that runs list_clients safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Savi Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_clients, this is the rule to start with:
list_clients 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 Savi Tools, apply this rule, and every list_clients call is checked against it from then on.
Questions about list_clients
List the subscriber’s clients with their billing profile, optionally filtered by a name/notes search. Answers "who are my clients?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
list_clients accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.
Register the Savi Tools MCP server in PolicyLayer and add a rule for list_clients: 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 Savi Tools. Nothing to install.
list_clients 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 list_clients 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 list_clients. 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.
list_clients is provided by the Savi Tools MCP server (https://getsavitools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Savi Tools, and thousands of servers like it.
This server
Across the catalogue