theme_set_constant
Set an integer constant entry on a Theme resource file and save it (e.g. h_separation for a BoxContainer). DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/theme-set-constant.md
What theme_set_constant does on Breakpoint
AI agents use theme_set_constant 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. h_separation, margin_left |
path | string | Yes | Theme res:// path |
value | integer | Yes | Integer constant value |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
theme_type | string | Yes | Theme type the item belongs to, e.g. HBoxContainer, MarginContainer |
Parameters from the server's own tool schema.
Why theme_set_constant is rated Medium
While the tool writes to a file and saves changes, the action is reversible (a subsequent call can change the value back) and is gated by confirmation, making it a Write operation rather than Destructive. The blast radius is medium—misuse could corrupt theme resources or render UI elements incorrectly, but the operation is not irreversible and can be undone.
From the tool's definition The description states it "Set[s] an integer constant entry on a Theme resource file and save[s] it", which modifies file content.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs theme_set_constant 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_constant, this is the rule to start with:
theme_set_constant 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_constant call is checked against it from then on.
Questions about theme_set_constant
Set an integer constant entry on a Theme resource file and save it (e.g. h_separation for a BoxContainer). DESTRUCTIVE (writes a file) — gated by confirmation. 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_constant accepts 5 parameters: name, path, value, confirm, theme_type. Required: name, path, value, 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_constant: 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_constant 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_constant 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_constant. 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_constant 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