get_site_brand

Read one site's brand identity — brandName, description, industry, targetAudience, tone, CTA URL/labels, market, products, keywords, topicScope, imageQueries. Call before update_site_brand so you send back the full value of any list you intend to change (writes replace a list, they do not append).

SERVERA3plus SOURCEa3plus-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a3plus-mcp/get-site-brand.md

WHAT IT DOES

What get_site_brand does on A3plus

AI agents call get_site_brand to retrieve information from A3plus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`siteId`	string	Yes	The A3Plus site ID.

Parameters from the server's own tool schema.

RISK

Why get_site_brand is rated Low

Even though get_site_brand only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_site_brand Allowed

get_site_brand is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_site_brand": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_site_brand

What does the get_site_brand tool do? +

What parameters does get_site_brand accept? +

get_site_brand accepts 1 parameter: siteId. Required: siteId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_site_brand? +

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

get_site_brand is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_site_brand? +

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

Set action: deny in the PolicyLayer policy for get_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 get_site_brand? +

get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →