New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

invoices_list_invoice_schedules

List schedules

SERVERGhl SOURCE@aiwerk/mcp-server-ghl
Low RISK CLASS
Category Read
Parameters 92 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/invoices-list-invoice-schedules.md

What invoices_list_invoice_schedules does on Ghl

AI agents call invoices_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.

ParameterTypeRequiredDescription
altId string location Id / company Id based on altType Defaults to GHL_LOCATION_ID when omitted.
endAt string endAt in YYYY-MM-DD format
limit string Yes Limit the number of items to return
offset string Yes Number of items to skip
search string To search for an invoice by id / name / email / phoneNo
status string status to be filtered
altType string Alt Type Defaults to GHL_LOCATION_ID when omitted.
startAt string startAt in YYYY-MM-DD format
paymentMode string payment mode

Parameters from the server's own tool schema.

Why invoices_list_invoice_schedules is rated Low

Even though invoices_list_invoice_schedules only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about invoices_list_invoice_schedules

What does the invoices_list_invoice_schedules tool do? +

List schedules. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does invoices_list_invoice_schedules accept? +

invoices_list_invoice_schedules accepts 9 parameters: altId, endAt, limit, offset, search, status, altType, startAt, paymentMode. Required: limit, offset. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on invoices_list_invoice_schedules? +

Register the Ghl MCP server in PolicyLayer and add a rule for invoices_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.

What risk level is invoices_list_invoice_schedules? +

invoices_list_invoice_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit invoices_list_invoice_schedules? +

Yes. Add a rate_limit block to the invoices_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.

How do I block invoices_list_invoice_schedules completely? +

Set action: deny in the PolicyLayer policy for invoices_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.

What MCP server provides invoices_list_invoice_schedules? +

invoices_list_invoice_schedules is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.