delete_custom_theme
Deletes the custom theme specified by the Id. Requires Cloud Analytics Admin permission.
This record as markdown: /tools/doit/delete-custom-theme.md
What delete_custom_theme does on Doit
AI agents call delete_custom_theme to permanently remove resources in Doit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
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 delete_custom_theme is rated Critical
An AI agent that decides to call delete_custom_theme doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Doit is gone. There is no undo for destructive operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs delete_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 delete_custom_theme, this is the rule to start with:
delete_custom_theme is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every delete_custom_theme call is checked against it from then on.
Questions about delete_custom_theme
Deletes the custom theme specified by the Id. Requires Cloud Analytics Admin permission. It is categorised as a Destructive tool in the Doit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_custom_theme accepts 2 parameters: id, customerContext. Required: id. 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 delete_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.
delete_custom_theme is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue