Delete a shipping carrier
AI agents call ghl_delete_shipping_carrier to permanently remove resources in GoHighLevel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a shipping carrier record, which cannot be undone. This is a destructive action that could disrupt business operations if executed incorrectly (e.g., deleting an active carrier used by pending orders). While not as critical as deleting customer data or financial records, it causes irreversible loss of configuration data.
From the tool's definition Tool name contains 'delete' and description states 'Delete a shipping carrier'. This is an irreversible deletion operation that removes a shipping carrier configuration.
Documented attack patterns abuse exactly the kind of access ghl_delete_shipping_carrier 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 ghl_delete_shipping_carrier:
{
"version": "1",
"default": "deny",
"hide": [
"ghl_delete_shipping_carrier"
]
} ghl_delete_shipping_carrier disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a shipping carrier. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_delete_shipping_carrier: 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.
ghl_delete_shipping_carrier is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ghl_delete_shipping_carrier 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 ghl_delete_shipping_carrier. 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.
ghl_delete_shipping_carrier is provided by the GoHighLevel MCP Server MCP server (mastanley13/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
255 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.