rename_site

SERVERA3plus SOURCEa3plus-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a3plus-mcp/rename-site.md

WHAT IT DOES

What rename_site does on A3plus

AI agents use rename_site 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	Yes	New site label, 1–200 characters.
`siteId`	string	Yes	The A3Plus site ID from list_sites.

Parameters from the server's own tool schema.

RISK

Why rename_site is rated Medium

An AI agent can call rename_site 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

RECOMMENDED RULE

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

rename_site Rate-limited

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

FAQ

Questions about rename_site

What does the rename_site tool do? +

Rename ONE site's dashboard label — the name shown in the project site list and returned by list_sites (e.g. change "Site 1" to "Acme Blog"). This is the internal/organisational name only; it does NOT change the public brand name rendered on the live site (that is set during enrichment). To relabel many sites at once, use rename_sites instead (one round-trip). 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 rename_site accept? +

rename_site accepts 2 parameters: name, siteId. Required: name, siteId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rename_site? +

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

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

Can I rate-limit rename_site? +

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

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

rename_site 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →