create_project
This token is project-scoped. Pass projectId to list_sites, or call list_projects to discover the bound project. Create a new A3Plus project carrying the SHARED brand profile + FAQ (the data filled once per brand in the intake spreadsheet). Sites are added separately with create_sites. Requires a...
This record as markdown: /tools/a3plus-mcp/create-project.md
What create_project does on A3plus
AI agents use create_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 | — | Project name. Optional — defaults to brand_name. |
dryRun | boolean | — | Preview only — create nothing. |
faqGroups | array | — | FAQ groups. Merge each answer from the spreadsheet (confirmed-over-draft) BEFORE sending — send only final Q/A text. |
brandProfile | object | Yes | Shared brand fields (spreadsheet api_key names). |
Parameters from the server's own tool schema.
Why create_project is rated Medium
An AI agent can call create_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 (24 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_project, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every create_project call is checked against it from then on.
Questions about create_project
This token is project-scoped. Pass projectId to list_sites, or call list_projects to discover the bound project. Create a new A3Plus project carrying the SHARED brand profile + FAQ (the data filled once per brand in the intake spreadsheet). Sites are added separately with create_sites. Requires a Personal Access Token (ak_user_…). Field names match the spreadsheet api_key column. Set dryRun:true to preview the mapped brand profile + see which required fields are still missing, without creating anything. 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.
create_project accepts 4 parameters: name, dryRun, faqGroups, brandProfile. Required: brandProfile. 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 create_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.
create_project 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue