This record as markdown: /tools/aiwerk-mcp-server-ghl/brand-boards-update-brand-board.md
What brand_boards_update_brand_board does on Ghl
AI agents use brand_boards_update_brand_board to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Brand board ID to update, retrieve, or delete |
name | string | — | Name of the brand board |
fonts | array | — | Array of fonts for the brand board |
logos | array | — | Array of logos for the brand board |
colors | array | — | Array of colors for the brand board |
default | boolean | — | Set as the default brand board for this location |
parentId | string | — | Parent folder ID in media library (reserved for future use) |
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_update_brand_board is rated Medium
An AI agent can call brand_boards_update_brand_board faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs brand_boards_update_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_update_brand_board, this is the rule to start with:
brand_boards_update_brand_board stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every brand_boards_update_brand_board call is checked against it from then on.
Questions about brand_boards_update_brand_board
Update a Brand Board. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
brand_boards_update_brand_board accepts 8 parameters: id, name, fonts, logos, colors, default, parentId, 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_update_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_update_brand_board is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the brand_boards_update_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_update_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_update_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.
This server
Across the catalogue