This record as markdown: /tools/ghl/list-invoice-schedules.md
What list_invoice_schedules does on Ghl
AI agents call list_invoice_schedules to retrieve information from Ghl 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 |
|---|---|---|---|
altId | string | — | Location ID |
limit | string | Yes | Number of results per page |
offset | string | Yes | Offset for pagination |
search | string | — | Search term |
status | string | — | Filter by status |
Parameters from the server's own tool schema.
Why list_invoice_schedules is rated Low
This tool queries and retrieves invoice schedule data without modifying, deleting, or executing any operations. It is a straightforward read/list operation typical of data retrieval APIs. The low severity reflects minimal risk even if an AI agent misuses it—reading invoice schedules poses no destructive or financial harm by itself, though the data may be sensitive in context.
From the tool's definition Tool name 'list_invoice_schedules' and description 'List all invoice schedules' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_invoice_schedules safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_invoice_schedules, this is the rule to start with:
list_invoice_schedules 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 Ghl, apply this rule, and every list_invoice_schedules call is checked against it from then on.
Questions about list_invoice_schedules
List all invoice schedules. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
list_invoice_schedules accepts 5 parameters: altId, limit, offset, search, status. Required: limit, offset. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for list_invoice_schedules: 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 Ghl. Nothing to install.
list_invoice_schedules 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_invoice_schedules 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_invoice_schedules. 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_invoice_schedules is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue