listBrandKits
List an organisation's BRAND KITS (palette/fonts/logo), newest first. Use a returned id as brandKitId for a design call or setDefaultBrandKit. Auth: can_admin_org.
This record as markdown: /tools/io-stablebaseline-sb/listbrandkits.md
What listBrandKits does on Stable Baseline
AI agents call listBrandKits to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
organizationId | string | Yes |
Parameters from the server's own tool schema.
Why listBrandKits is rated Low
This tool retrieves organizational branding assets without modifying, deleting, or executing any operations. It is a read-only query operation. The requirement for 'can_admin_org' auth indicates access control but does not elevate the category beyond Read. Severity is low because misuse would only expose metadata about brand guidelines, not cause harm to systems or data.
From the tool's definition Tool name 'listBrandKits' and description 'List an organisation's BRAND KITS' indicates a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs listBrandKits 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 listBrandKits, this is the rule to start with:
listBrandKits is read-only, so it stays allowed. 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 listBrandKits call is checked against it from then on.
Questions about listBrandKits
List an organisation's BRAND KITS (palette/fonts/logo), newest first. Use a returned id as brandKitId for a design call or setDefaultBrandKit. Auth: can_admin_org. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listBrandKits accepts 1 parameter: organizationId. Required: organizationId. 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 listBrandKits: 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.
listBrandKits is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listBrandKits 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 listBrandKits. 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.
listBrandKits 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