rename_sites
This token is project-scoped. Pass projectId to list_sites, or call list_projects to discover the bound project. Batch-rename multiple sites' dashboard labels in ONE call — the efficient way to relabel many sites (e.g. map "Site 1…N" to your own names) without one request per site. Pass renames a...
This record as markdown: /tools/a3plus-mcp/rename-sites.md
What rename_sites does on A3plus
AI agents use rename_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 |
|---|---|---|---|
renames | array | Yes | Rename instructions (max 500). Each entry maps a siteId to its new label (1–200 chars). |
projectId | string | Yes | The A3Plus project ID. Required unless A3PLUS_PROJECT_ID env var is set. |
Parameters from the server's own tool schema.
Why rename_sites is rated Medium
An AI agent can call rename_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.
Attacks that exploit this kind of access
The rule that runs rename_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 rename_sites, this is the rule to start with:
rename_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 rename_sites call is checked against it from then on.
Questions about rename_sites
This token is project-scoped. Pass projectId to list_sites, or call list_projects to discover the bound project. Batch-rename multiple sites' dashboard labels in ONE call — the efficient way to relabel many sites (e.g. map "Site 1…N" to your own names) without one request per site. Pass renames as an array of { siteId, name }. Every site must belong to the given project; the response reports per-site which renames applied and which failed (and why), so a single bad siteId never aborts the rest. Edits the internal/dashboard label only, not the public brand name. TIP: call list_sites first to get the siteIds + current names, then map them to the new names. 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.
rename_sites accepts 2 parameters: renames, projectId. Required: renames, 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 rename_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.
rename_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 rename_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 rename_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.
rename_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