This record as markdown: /tools/ghl/get-invoice-schedule.md
What get_invoice_schedule does on Ghl
AI agents call get_invoice_schedule 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 |
scheduleId | string | Yes | Schedule ID |
Parameters from the server's own tool schema.
Why get_invoice_schedule is rated Low
This tool retrieves invoice schedule data by identifier. The verb 'get' and lack of any modification, deletion, or financial transaction language indicate a read-only query operation. While invoice data may be sensitive, the tool itself performs no destructive, write, execute, or financial action — it only retrieves existing information.
From the tool's definition Tool name is 'get_invoice_schedule' and description states 'Get invoice schedule by ID' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_invoice_schedule 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 get_invoice_schedule, this is the rule to start with:
get_invoice_schedule 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 get_invoice_schedule call is checked against it from then on.
Questions about get_invoice_schedule
Get invoice schedule by ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_invoice_schedule accepts 2 parameters: altId, scheduleId. Required: scheduleId. 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 get_invoice_schedule: 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.
get_invoice_schedule 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_invoice_schedule 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_invoice_schedule. 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_invoice_schedule 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