theme_set_color
Set a color entry on a Theme resource file and save it (e.g. font_color for the Button type). DESTRUCTIVE (writes a file) — gated by confirmation. 'color' is [r,g,b] or [r,g,b,a] with components 0..1.
This record as markdown: /tools/breakpoint-mcp/theme-set-color.md
What theme_set_color does on Breakpoint
AI agents use theme_set_color to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Theme item name, e.g. font_color |
path | string | Yes | Theme res:// path |
color | array | Yes | [r,g,b] or [r,g,b,a], components 0..1 |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
theme_type | string | Yes | Theme type the item belongs to, e.g. Button, Label |
Parameters from the server's own tool schema.
Why theme_set_color is rated Medium
This tool creates or modifies data (a Theme resource file) reversibly. While the description uses the word 'DESTRUCTIVE', the modification is not truly irreversible—theme color entries can be re-edited or restored from backups. The confirmation gate further reduces risk.
From the tool's definition Tool description states: 'Set a color entry on a Theme resource file and save it' — modifies a configuration file.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs theme_set_color safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theme_set_color, this is the rule to start with:
theme_set_color 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 Breakpoint, apply this rule, and every theme_set_color call is checked against it from then on.
Questions about theme_set_color
Set a color entry on a Theme resource file and save it (e.g. font_color for the Button type). DESTRUCTIVE (writes a file) — gated by confirmation. 'color' is [r,g,b] or [r,g,b,a] with components 0..1. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
theme_set_color accepts 5 parameters: name, path, color, confirm, theme_type. Required: name, path, color, theme_type. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for theme_set_color: 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 Breakpoint. Nothing to install.
theme_set_color 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 theme_set_color 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 theme_set_color. 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.
theme_set_color is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue