This record as markdown: /tools/aiwerk-mcp-server-ghl/brand-boards-delete-brand-board.md
What brand_boards_delete_brand_board does on Ghl
AI agents call brand_boards_delete_brand_board to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Brand board ID to update, retrieve, or delete |
locationId | string | — | Location ID where the brand board exists Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why brand_boards_delete_brand_board is rated Critical
An AI agent that decides to call brand_boards_delete_brand_board doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs brand_boards_delete_brand_board 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 brand_boards_delete_brand_board, this is the rule to start with:
brand_boards_delete_brand_board is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every brand_boards_delete_brand_board call is checked against it from then on.
Questions about brand_boards_delete_brand_board
Delete a Brand Board. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
brand_boards_delete_brand_board accepts 2 parameters: id, locationId. Required: id. 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 brand_boards_delete_brand_board: 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.
brand_boards_delete_brand_board 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 brand_boards_delete_brand_board 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 brand_boards_delete_brand_board. 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.
brand_boards_delete_brand_board 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.
Across the catalogue