createBrandKit

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/createbrandkit.md

WHAT IT DOES

What createBrandKit does on Stable Baseline

AI agents use createBrandKit 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
`name`	string	Yes	Display name (e.g. the brand/company name).
`tokens`	object	—	Explicit DTCG brand tokens { color:{brand:{primary,primaryText,ink,bg,surface,muted,border,positive,warning,negative}}, font:{heading,body} }. Omit to extract f
`logoUrl`	string	—	Image URL of the logo to extract palette/fonts from (PNG/JPG/SVG). Omit if passing officeUrl or tokens.
`guidance`	string	—	Optional extra guidance for the extractor (e.g. 'use the teal, not the grey').
`officeUrl`	string	—	URL of an existing .pptx or .docx to extract the brand from (theme colours + fonts + logo + watermark + embedded fonts). Max 25MB. Omit if passing logoUrl or to
`organizationId`	string	Yes	Org that owns the kit.
`setDefaultScope`	string	—	Optionally set the new kit as default at this scope.
`setDefaultScopeId`	string	—	Workspace/project id when setDefaultScope is workspace/project.

Parameters from the server's own tool schema.

RISK

Why createBrandKit is rated Medium

This is a Write operation: it creates and stores organizational branding configuration that modifies how the system generates outputs going forward. While the tool has administrative scope (can_admin_org auth requirement), it does not irreversibly delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).

From the tool's definition Creates a per-org BRAND KIT with explicit parameters (logoUrl, officeUrl, tokens) that are persisted and auto-applied to future outputs. The tool allows uploading/storing branding assets and configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs createBrandKit 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 createBrandKit, this is the rule to start with:

createBrandKit Rate-limited

createBrandKit 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createBrandKit": {
      "limits": [
        {
          "counter": "createbrandkit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every createBrandKit call is checked against it from then on.

FAQ

Questions about createBrandKit

What does the createBrandKit tool do? +

Create a per-org BRAND KIT so Stable Baseline outputs come out fully on-brand. Upload your branding and it is auto-applied: pass a logoUrl (as little as your logo, and the vision model AUTO-EXTRACTS your palette and fonts), or an officeUrl (an existing .pptx/.docx, from which it extracts theme colours, fonts, logo, watermark and the embedded font files), or explicit tokens. The kit themes branded-executive slides AND document exports (PDF, Word, PowerPoint). Auth: can_admin_org. Tiered: free 0, pro 1, enterprise unlimited. Optionally set it as the default at a scope in one call. 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.

What parameters does createBrandKit accept? +

createBrandKit accepts 8 parameters: name, tokens, logoUrl, guidance, officeUrl, organizationId, setDefaultScope, setDefaultScopeId. Required: name, organizationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on createBrandKit? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for createBrandKit: 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.

What risk level is createBrandKit? +

createBrandKit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createBrandKit? +

Yes. Add a rate_limit block to the createBrandKit 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.

How do I block createBrandKit completely? +

Set action: deny in the PolicyLayer policy for createBrandKit. 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.

What MCP server provides createBrandKit? +

createBrandKit 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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →