set_active_theme
Use this when the user wants to change the authenticated user’s active Cloud Analytics color theme. Accepts a custom theme ID or supported preset ID or the sentinel "default" to revert to the built-in default. Changes apply immediately. Requires Cloud Analytics edit permission. Create new themes ...
This record as markdown: /tools/doit/set-active-theme.md
What set_active_theme does on Doit
AI agents use set_active_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 |
|---|---|---|---|
themeId | string | Yes | The ID of a custom theme or a supported preset theme to set as active for the authenticated user, or the reserved sentinel "default" to revert to the built-in d |
Parameters from the server's own tool schema.
Why set_active_theme is rated Medium
An AI agent can call set_active_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.
Attacks that exploit this kind of access
The rule that runs set_active_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 set_active_theme, this is the rule to start with:
set_active_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 set_active_theme call is checked against it from then on.
Questions about set_active_theme
Use this when the user wants to change the authenticated user’s active Cloud Analytics color theme. Accepts a custom theme ID or supported preset ID or the sentinel "default" to revert to the built-in default. Changes apply immediately. Requires Cloud Analytics edit permission. Create new themes with create_custom_theme. Do NOT use this to retrieve the current active theme (use get_active_theme) or to update theme colors (use update_theme). 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.
set_active_theme accepts 1 parameter: themeId. Required: themeId. 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 set_active_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.
set_active_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 set_active_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 set_active_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.
set_active_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