Get invoice schedule by ID
AI agents call get_invoice_schedule to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves invoice schedule information by identifier. It is purely informational—reading data about invoice schedules rather than creating, modifying, deleting, or processing payments. While it accesses financial-domain data (invoices), it performs no financial operations (no transfers, charges, or commitments). Classification as Read is appropriate given the low-impact nature of data retrieval.
From the tool's definition Tool name 'get_invoice_schedule' and description 'Get invoice schedule by ID' indicate a retrieval operation with the verb 'Get', which retrieves existing data without modification, deletion, or execution of financial transactions.
Attacks that exploit this kind of access
Get invoice schedule by ID. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →