List all fulfillment history of an order
AI agents call list-order-fulfillment 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 fulfillment history records associated with an order. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal—an AI agent using this tool can only access order fulfillment information it is already authorized to view.
From the tool's definition Tool name 'list-order-fulfillment' and description 'List all fulfillment history of an order' indicate retrieval of historical data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list-order-fulfillment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-order-fulfillment:
{
"version": "1",
"default": "deny",
"tools": {
"list-order-fulfillment": {}
}
} list-order-fulfillment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all fulfillment history of an order. 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 list-order-fulfillment: 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.
list-order-fulfillment 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-order-fulfillment 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-order-fulfillment. 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-order-fulfillment is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.