update_site_brand

SERVERA3plus SOURCEa3plus-mcp

Medium RISK CLASS

Category Write

Parameters 121 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-brand.md

WHAT IT DOES

What update_site_brand does on A3plus

AI agents use update_site_brand 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
`tone`	string	—	e.g. friendly, authoritative.
`ctaUrl`	string	—	Where CTA buttons point.
`market`	string	—
`siteId`	string	Yes	The A3Plus site ID.
`industry`	string	—
`keywords`	array	—	Baseline SEO keywords.
`products`	array	—
`brandName`	string	—	Display name. Cannot be blanked — packs fall back to it for the page title.
`topicScope`	array	—	Niche anchor; [0] drives trend seeding.
`description`	string	—	What the brand is. Feeds article generation context.
`imageQueries`	array	—	Stock/generated image themes.
`marketCountry`	string	—

Parameters from the server's own tool schema.

RISK

Why update_site_brand is rated Medium

An AI agent can call update_site_brand 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 signalsHigh parameter count (16 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_site_brand 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_brand, this is the rule to start with:

update_site_brand Rate-limited

update_site_brand 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_brand": {
      "limits": [
        {
          "counter": "update_site_brand_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_brand call is checked against it from then on.

FAQ

Questions about update_site_brand

What does the update_site_brand tool do? +

Update ONE site's brand identity. This is per-site — unlike update_project, which fans the same values out to every site in the project. Editable: brandName, description, industry, targetAudience, tone, mainWebsiteUrl, ctaUrl, ctaTextOptions, market, marketCountry, marketDetails, products, keywords, topicScope, imageQueries. Arrays REPLACE the stored list — read with get_site_brand first and send the full array. topicScope is the trend-hunter niche anchor: topicScope[0] decides which trends the auto-article pipeline seeds from, so a stale value keeps producing off-brand articles after a rebrand — fix it here. NOT editable here (the call is rejected, not silently ignored): logoUrl/faviconUrl → update_site_branding; heroTitle/tagline/features/navLinks/packLabels → update_site_content; language → needs a re-enrich, since changing it does not re-translate existing copy. 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_brand accept? +

update_site_brand accepts 12 parameters: tone, ctaUrl, market, siteId, industry, keywords, products, brandName, topicScope, description, imageQueries, marketCountry. 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_brand? +

Register the A3plus MCP server in PolicyLayer and add a rule for update_site_brand: 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_brand? +

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

Can I rate-limit update_site_brand? +

Yes. Add a rate_limit block to the update_site_brand 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_brand completely? +

Set action: deny in the PolicyLayer policy for update_site_brand. 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_brand? +

update_site_brand 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 →