update_site_branding

SERVERA3plus SOURCEa3plus-mcp

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a3plus-mcp/update-site-branding.md

WHAT IT DOES

What update_site_branding does on A3plus

AI agents use update_site_branding to create or update resources in A3plus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A3plus environment.

Parameter	Type	Required	Description
`hero`	object	—	New homepage hero BACKGROUND image (wide landscape, ~1440×720+ recommended). `{ url }` OR `{ base64 }`. Pass null to clear (reverts to a stock placeholder).
`logo`	object	—	New logo image. `{ url }` (server fetches it) OR `{ base64 }`. Pass null to clear.
`siteId`	string	Yes	The A3Plus site ID from list_sites.
`favicon`	object	—	New favicon image (PNG recommended). `{ url }` OR `{ base64 }`. Pass null to clear.

Parameters from the server's own tool schema.

RISK

Why update_site_branding is rated Medium

An AI agent can call update_site_branding faster than any human can review: one bad instruction and it creates or modifies resources in A3plus by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (logo.url) · High parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_site_branding safely

PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_site_branding, this is the rule to start with:

update_site_branding Rate-limited

update_site_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_site_branding": {
      "limits": [
        {
          "counter": "update_site_branding_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every update_site_branding call is checked against it from then on.

FAQ

Questions about update_site_branding

What does the update_site_branding tool do? +

Replace a site's logo, favicon and/or homepage hero background image. Changes take effect within a few minutes. Perfect for batch-swapping branding across many sites from your own image library: call once per site. Each image is RE-HOSTED to the A3Plus CDN, so it keeps working even if your source URL disappears — pass url (we fetch it) or base64 (raw bytes / data: URI). Formats: jpeg, png, webp, gif, avif (PNG recommended for favicon; SVG not accepted). Max 10 MB. Pass logo: null / favicon: null / hero: null to clear it (reverts to the site default). Use get_site_content to read the current logoUrl/faviconUrl first. It is categorised as a Write tool in the A3plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_site_branding accept? +

update_site_branding accepts 4 parameters: hero, logo, siteId, favicon. Required: siteId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_site_branding? +

Register the A3plus MCP server in PolicyLayer and add a rule for update_site_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 A3plus. Nothing to install.

What risk level is update_site_branding? +

update_site_branding is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_site_branding? +

Yes. Add a rate_limit block to the update_site_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.

How do I block update_site_branding completely? +

Set action: deny in the PolicyLayer policy for update_site_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.

What MCP server provides update_site_branding? +

update_site_branding is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on A3plus, and thousands of servers like it.

This server

All 61 A3plus tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →