clone_widget

SERVERElementify MCP SOURCEvamerli/elementify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vamerli-elementify-mcp/clone-widget.md

WHAT IT DOES

What clone_widget does on Elementify MCP

AI agents call clone_widget to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why clone_widget is rated Low

Even though clone_widget only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clone_widget Allowed

clone_widget is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clone_widget": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every clone_widget call is checked against it from then on.

FAQ

Questions about clone_widget

What does the clone_widget tool do? +

Clone a widget from a source page into a target page at a specific position. The source widget is deep-cloned with a new element ID. Global style references (__globals__, typography bindings) are carried over verbatim — the response includes a global_references list (enumeration only, NOT validated against the target page). Requires the TARGET page content_hash. NOTE: not idempotent — a repeated call inserts a second copy (no idempotency key, no retry). See ELM-IDEMP-001 for whether content_hash already covers the retry case before adding a second mechanism. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clone_widget? +

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

clone_widget is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clone_widget? +

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

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

clone_widget 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →