disable_custom_branding
[Account Management API 2] Disables custom branding for the tenant.
This record as markdown: /tools/acronis-platform-mcp/disable-custom-branding.md
What disable_custom_branding does on Acronis Platform
AI agents use disable_custom_branding to create or update resources in Acronis Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Acronis Platform environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | object | Yes | URI path parameters |
query | object | — | Query parameters |
Parameters from the server's own tool schema.
Why disable_custom_branding is rated Medium
An AI agent can call disable_custom_branding faster than any human can review: one bad instruction and it creates or modifies resources in Acronis Platform by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs disable_custom_branding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Acronis Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disable_custom_branding, this is the rule to start with:
disable_custom_branding 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 Acronis Platform, apply this rule, and every disable_custom_branding call is checked against it from then on.
Questions about disable_custom_branding
[Account Management API 2] Disables custom branding for the tenant. It is categorised as a Write tool in the Acronis Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
disable_custom_branding accepts 2 parameters: path, query. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Acronis Platform MCP server in PolicyLayer and add a rule for disable_custom_branding: 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 Acronis Platform. Nothing to install.
disable_custom_branding 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 disable_custom_branding 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 disable_custom_branding. 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.
disable_custom_branding is provided by the Acronis Platform MCP server (@acronis-platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Acronis Platform, and thousands of servers like it.
This server
Across the catalogue