common-convert-from-item-clone-by-id

WHAT IT DOES

What common-convert-from-item-clone-by-id does on SitecoreMCP

AI agents use common-convert-from-item-clone-by-id to create or update resources in SitecoreMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SitecoreMCP environment.

WHY IT NEEDS A POLICY

Why common-convert-from-item-clone-by-id needs a policy

This tool modifies existing data (converts a clone relationship) rather than creating entirely new data or destroying it. The conversion is reversible—the item could theoretically be re-cloned or the operation undone, placing it in the Write category. Severity is medium because incorrect use could disrupt content relationships in a Sitecore instance, but the effect is limited to a single item and recoverable.

From the tool's definition The tool 'converts an item from a clone to a fully independent item by its ID.' This is a modification operation that changes the state and structure of an item in Sitecore, making it reversible (a clone can be recreated).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

common-convert-from-item-clone-by-id Rate-limited

common-convert-from-item-clone-by-id 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": {
    "common-convert-from-item-clone-by-id": {
      "limits": [
        {
          "counter": "common-convert-from-item-clone-by-id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SitecoreMCP, so you can run agents against it safely.

FAQ

Questions about common-convert-from-item-clone-by-id

What does the common-convert-from-item-clone-by-id tool do? +

Converts an item from a clone to a fully independent item by its ID. It is categorised as a Write tool in the SitecoreMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on common-convert-from-item-clone-by-id? +

Register the Sitecore MCP server in PolicyLayer and add a rule for common-convert-from-item-clone-by-id: 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 SitecoreMCP. Nothing to install.

What risk level is common-convert-from-item-clone-by-id? +

common-convert-from-item-clone-by-id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit common-convert-from-item-clone-by-id? +

Yes. Add a rate_limit block to the common-convert-from-item-clone-by-id 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 common-convert-from-item-clone-by-id completely? +

Set action: deny in the PolicyLayer policy for common-convert-from-item-clone-by-id. 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 common-convert-from-item-clone-by-id? +

common-convert-from-item-clone-by-id is provided by the Sitecore MCP server (ramseur/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.