common-convert-from-item-clone-by-path

Converts an item from a clone to a fully independent item by its path.

Accepts file system path (path)

Part of the Mcp Sitecore MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@antonytm/mcp-sitecore-server Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use common-convert-from-item-clone-by-path to create or modify resources in Mcp Sitecore. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON COMMON-CONVERT-FROM-ITEM-CLONE-BY-PATH

Without a policy, an AI agent could call common-convert-from-item-clone-by-path repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Sitecore.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-antonytm-mcp-sitecore-server.yaml

tools:
  common-convert-from-item-clone-by-path:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Sitecore policy for all 153 tools.

// DETAILS

Tool Name common-convert-from-item-clone-by-path

Category Write

MCP Server Mcp Sitecore MCP Server

Risk Level Medium

// MORE MCP SITECORE TOOLS

Destructive common-remove-archive-item Destructive common-remove-base-template-by-id Destructive common-remove-base-template-by-path Destructive common-remove-item-version-by-id Destructive common-remove-item-version-by-path Destructive common-reset-item-field-by-id Destructive common-reset-item-field-by-path Destructive indexing-remove-search-index-item-by-id

View all 153 tools →

// RELATED READING

// FAQ

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

Converts an item from a clone to a fully independent item by its path.. It is categorised as a Write tool in the Mcp Sitecore 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-path? +

Add a rule in your Intercept YAML policy under the tools section for common-convert-from-item-clone-by-path. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sitecore MCP server.

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

common-convert-from-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-convert-from-item-clone-by-path? +

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

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

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

common-convert-from-item-clone-by-path

Enforce policies on Mcp Sitecore