update_site_content

SERVERA3plus SOURCEa3plus-mcp

Medium RISK CLASS

Category Write

Parameters 31 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-content.md

WHAT IT DOES

What update_site_content does on A3plus

AI agents use update_site_content 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
`home`	object	—	Home page copy fields to update (any subset).
`about`	object	—	About page copy fields to update (any subset).
`siteId`	string	Yes	The A3Plus site ID.

Parameters from the server's own tool schema.

RISK

Why update_site_content is rated Medium

An AI agent can call update_site_content 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 (28 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_site_content Rate-limited

update_site_content 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_content": {
      "limits": [
        {
          "counter": "update_site_content_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_content call is checked against it from then on.

FAQ

Questions about update_site_content

What does the update_site_content tool do? +

Update a site's visitor-facing page copy (home hero, "Why Choose Us" features, post-FAQ CTA block, header nav links, glossary + about page). Changes take effect within a few minutes. Pass home and/or about objects carrying only the fields you want to change; omitted fields are left untouched. Editable home fields: heroTitle, heroSubtitle, ctaText, tagline, metaDescription, shortDescription, featuresHeading, features, ctaSectionHeading, ctaSectionDescription, ctaSectionButtonText, navLinks, glossaryItems, mission, valuesHeading, aboutSubtitle, aboutStoryHeading, faqHeading, packLabels, socialLinks. IMPORTANT: the About page renders from the home object, so aboutSubtitle / aboutStoryHeading / mission / valuesHeading belong under home — putting them under about is accepted but never displayed. packLabels is a flat { slotKey: "translated text" } map for the pack's own UI strings (nav headings, section eyebrows, "Read more", legal link labels…). It MERGES: sending one key leaves the others alone. Use it to fix labels still rendering English on a non-English site — most pack labels are NOT declared in the pack manifest, so this is the only way to override them. Keys must match /^[A-Za-z0-9_]+$/. Editable about fields: aboutTitle, aboutText, aboutParagraphs (array of strings), metaDescription, shortDescription. Brand identity (brandName, industry) is not editable here (use update_project); logo/favicon/hero background image go through update_site_branding. Unknown fields are ignored. 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_content accept? +

update_site_content accepts 3 parameters: home, about, 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 update_site_content? +

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

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

Can I rate-limit update_site_content? +

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

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

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