rename_template

Rename an Elementor template.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vamerli-elementify-mcp/rename-template.md

WHAT IT DOES

What rename_template does on Elementify MCP

AI agents use rename_template to create or update resources in Elementify MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elementify MCP environment.

RISK

Why rename_template is rated Medium

Renaming a template is a write operation that modifies data reversibly. While it changes template state, it does not delete content (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions.

From the tool's definition Tool name 'rename_template' and description 'Rename an Elementor template' indicate modification of existing template metadata. This is a reversible operation that alters template properties without deletion or financial impact.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_template safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_template, this is the rule to start with:

rename_template Rate-limited

rename_template 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_template": {
      "limits": [
        {
          "counter": "rename_template_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 Elementify MCP, apply this rule, and every rename_template call is checked against it from then on.

FAQ

Questions about rename_template

What does the rename_template tool do? +

Rename an Elementor template. It is categorised as a Write tool in the Elementify MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_template? +

Register the Elementify MCP server in PolicyLayer and add a rule for rename_template: 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 Elementify MCP. Nothing to install.

What risk level is rename_template? +

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

Can I rate-limit rename_template? +

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

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

rename_template is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 269 Elementify tools →

Across the catalogue

The MCP Attack Database →

Guides

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