create_custom_theme
Creates a new custom color theme. Requires Cloud Analytics Admin permission.
This record as markdown: /tools/doit/create-custom-theme.md
What create_custom_theme does on Doit
AI agents use create_custom_theme to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The display name of the custom theme. |
colors | object | Yes | Palettes for light and dark display modes. Each palette must contain between 1 and 32 hex colors. |
primaryColor | string | Yes | A color in hex notation. Accepts `#RGB`, `#RRGGBB`, or `#RRGGBBAA`. |
customerContext | string | — | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |
Parameters from the server's own tool schema.
Why create_custom_theme is rated Medium
An AI agent can call create_custom_theme faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_custom_theme safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_custom_theme, this is the rule to start with:
create_custom_theme 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 Doit, apply this rule, and every create_custom_theme call is checked against it from then on.
Questions about create_custom_theme
Creates a new custom color theme. Requires Cloud Analytics Admin permission. It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_custom_theme accepts 4 parameters: name, colors, primaryColor, customerContext. Required: name, colors, primaryColor. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for create_custom_theme: 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 Doit. Nothing to install.
create_custom_theme 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 create_custom_theme 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 create_custom_theme. 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.
create_custom_theme is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue