setDefaultBrandKit
Set or clear the default BRAND KIT at a scope: organization, workspace, or project. Defaults cascade most-specific-first (a per-board/document override beats project beats workspace beats organization). Pass brandKitId:null to clear. Auth: org owner/admin.
This record as markdown: /tools/io-stablebaseline-sb/setdefaultbrandkit.md
What setDefaultBrandKit does on Stable Baseline
AI agents use setDefaultBrandKit to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
scope | string | Yes | |
scopeId | string | Yes | The org/workspace/project id for the chosen scope. |
brandKitId | string | null | — | Brand kit to make default, or null to clear. |
Parameters from the server's own tool schema.
Why setDefaultBrandKit is rated Medium
This tool creates or modifies branding configuration settings in a cascading hierarchy across organizational scopes. While it changes system state, the modifications are reversible and the blast radius is limited to visual presentation and branding consistency rather than destructive data loss or financial impact.
From the tool's definition Tool description states "Set or clear the default BRAND KIT" which modifies configuration settings. The action is reversible (can be cleared by passing brandKitId:null), and affects visual/branding defaults rather than core data deletion.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs setDefaultBrandKit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setDefaultBrandKit, this is the rule to start with:
setDefaultBrandKit 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 Stable Baseline, apply this rule, and every setDefaultBrandKit call is checked against it from then on.
Questions about setDefaultBrandKit
Set or clear the default BRAND KIT at a scope: organization, workspace, or project. Defaults cascade most-specific-first (a per-board/document override beats project beats workspace beats organization). Pass brandKitId:null to clear. Auth: org owner/admin. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
setDefaultBrandKit accepts 3 parameters: scope, scopeId, brandKitId. Required: scope, scopeId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for setDefaultBrandKit: 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 Stable Baseline. Nothing to install.
setDefaultBrandKit 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 setDefaultBrandKit 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 setDefaultBrandKit. 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.
setDefaultBrandKit is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue