common-new-item-clone-by-path · Sitecore MCP: Risk & Policy

WHAT IT DOES

What common-new-item-clone-by-path does on SitecoreMCP

AI agents use common-new-item-clone-by-path 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-new-item-clone-by-path needs a policy

This tool creates a new item (a clone) in the Sitecore CMS, which is a reversible write operation. It does not delete or overwrite existing data, execute arbitrary code, or involve financial transactions. The clone can presumably be removed later, making it a standard Write action. Severity is medium because creating items in a CMS could affect content delivery if misused.

From the tool's definition Creates a new item clone based on the item provided by its path

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

common-new-item-clone-by-path Rate-limited

common-new-item-clone-by-path 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-new-item-clone-by-path": {
      "limits": [
        {
          "counter": "common-new-item-clone-by-path_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-new-item-clone-by-path

What does the common-new-item-clone-by-path tool do? +

Creates a new item clone based on the item provided by its path. 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-new-item-clone-by-path? +

Register the Sitecore MCP server in PolicyLayer and add a rule for common-new-item-clone-by-path: 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-new-item-clone-by-path? +

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

Can I rate-limit common-new-item-clone-by-path? +

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

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

common-new-item-clone-by-path 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.