update_project

SERVERA3plus SOURCEa3plus-mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_project does on A3plus

AI agents use update_project 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
`name`	string	—	Rename the project (optional).
`faqGroups`	array	—	Replace the FAQ groups. [{ group_name, tag?, items: [{ question, answer }] }].
`projectId`	string	Yes	The A3Plus project ID.
`companyInfo`	object	—	Operating-company contact info shown in the site footer Contact block and substituted into legal pages (Privacy / Terms / Disclaimer / Contact). All optional —
`brandProfile`	object	—	Partial brand fields to change (spreadsheet api_key names): brand_name, industry, content_language, market_country, market_details, main_website_url, brand_desc
`syncExistingSites`	boolean	—	Default true — also apply to existing sites. false = only affect future sites.
`regenerateLegalPages`	boolean	—	Default false. When companyInfo changed, set true to reset every site's cached legal pages so they regenerate with the NEW values on next visit. WARNING: also d

Parameters from the server's own tool schema.

RISK

Why update_project is rated Medium

An AI agent can call update_project 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 (15 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_project Rate-limited

update_project 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_project": {
      "limits": [
        {
          "counter": "update_project_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_project call is checked against it from then on.

FAQ

Questions about update_project

What does the update_project tool do? +

Update a project's shared brand profile, company/legal contact info, and/or FAQ (the data behind the dashboard "Brand Profile" + "FAQ Settings" panels). Field names match the spreadsheet api_key column; send ONLY the fields you want to change (merged, not replaced). companyInfo (company_name / contact_email / country) feeds the footer Contact block and legal-page variables on every site — filling it matters for YMYL trust signals (Google flags missing operator info). By default the changes also propagate to every existing site in the project (identity + FAQ only — per-site AI copy is never touched); pass syncExistingSites:false to change just the project default for future sites. 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_project accept? +

update_project accepts 7 parameters: name, faqGroups, projectId, companyInfo, brandProfile, syncExistingSites, regenerateLegalPages. Required: projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_project? +

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

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

Can I rate-limit update_project? +

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

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

update_project 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

create_project on Stitch MCP Server →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 →