apply_brand_kit
Swap the brand kit on an existing document. Updates metadata.brandKitId + metadata.customColors so deployed renders pick up the new theme automatically (semantic Tailwind classes do the work — no AI needed). Pass \
This record as markdown: /tools/cloud-easybits-easybits/apply-brand-kit.md
What apply_brand_kit does on EasyBits
AI agents use apply_brand_kit to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why apply_brand_kit is rated Medium
Modifies document metadata reversibly; affects styling but no data deletion or execution risk.
From the tool's definition Swap brand kit, updates metadata.brandKitId + metadata.customColors on document.
Attacks that exploit this kind of access
The rule that runs apply_brand_kit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apply_brand_kit, this is the rule to start with:
apply_brand_kit 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 EasyBits, apply this rule, and every apply_brand_kit call is checked against it from then on.
Questions about apply_brand_kit
Swap the brand kit on an existing document. Updates metadata.brandKitId + metadata.customColors so deployed renders pick up the new theme automatically (semantic Tailwind classes do the work — no AI needed). Pass \. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for apply_brand_kit: 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 EasyBits. Nothing to install.
apply_brand_kit 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 apply_brand_kit 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 apply_brand_kit. 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.
apply_brand_kit is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue