sync_project_faq
Set the SAME /faq Q&A list on EVERY site in the project in ONE call — update the FAQ once, propagate to all site pages (req 4a). Writes each site's /faq page + FAQPage structured data. NOTE: this syncs SITE PAGES only; already-published ARTICLES bake their own FAQ into the body and are NOT modifi...
This record as markdown: /tools/a3plus-mcp/sync-project-faq.md
What sync_project_faq does on A3plus
AI agents use sync_project_faq 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 |
|---|---|---|---|
items | array | Yes | The FULL Q&A list to set on every site (replaces the existing list). Max 50. |
projectId | string | Yes | The A3Plus project ID. |
Parameters from the server's own tool schema.
Why sync_project_faq is rated Medium
An AI agent can call sync_project_faq 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs sync_project_faq 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 sync_project_faq, this is the rule to start with:
sync_project_faq 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.
The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every sync_project_faq call is checked against it from then on.
Questions about sync_project_faq
Set the SAME /faq Q&A list on EVERY site in the project in ONE call — update the FAQ once, propagate to all site pages (req 4a). Writes each site's /faq page + FAQPage structured data. NOTE: this syncs SITE PAGES only; already-published ARTICLES bake their own FAQ into the body and are NOT modified here (article-level sync ships in a later version). Takes effect within a few minutes. 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.
sync_project_faq accepts 2 parameters: items, projectId. Required: items, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for sync_project_faq: 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.
sync_project_faq is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_project_faq 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.
Set action: deny in the PolicyLayer policy for sync_project_faq. 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.
sync_project_faq 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.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue