create_sites
Batch-create sites in a project. YOU supply each site's enriched copy + chosen pack; the A3Plus backend runs NO copy-generation AI (it skips enrichment because you provided the content). The shared brand profile + FAQ already live on the project (create_project) — do NOT repeat them here. Each si...
This record as markdown: /tools/a3plus-mcp/create-sites.md
What create_sites does on A3plus
AI agents use create_sites 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 |
|---|---|---|---|
sites | array | Yes | One entry per site to create. |
dryRun | boolean | — | Validate + return the plan without creating anything. Do this first. |
projectId | string | Yes | Target project (from list_projects / create_project). Sites can be added to existing projects too. |
Parameters from the server's own tool schema.
Why create_sites is rated Medium
An AI agent can call create_sites 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 signalsAccepts raw HTML/template content (sites[].content) · High parameter count (25 properties)
Attacks that exploit this kind of access
The rule that runs create_sites 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_sites, this is the rule to start with:
create_sites 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_sites call is checked against it from then on.
Questions about create_sites
Batch-create sites in a project. YOU supply each site's enriched copy + chosen pack; the A3Plus backend runs NO copy-generation AI (it skips enrichment because you provided the content). The shared brand profile + FAQ already live on the project (create_project) — do NOT repeat them here. Each site needs ALL ~13 content fields (call get_intake_schema for the list); a missing field rejects the whole batch with exactly what is missing, so you can fix and retry. Vary copy AND pack per site so siblings differ. ALWAYS dryRun:true first to preflight (names, pack assignment, warnings), report the plan to the user, then send for real. 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_sites accepts 3 parameters: sites, dryRun, projectId. Required: sites, 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 create_sites: 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_sites 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_sites 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_sites. 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_sites 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