common-reset-item-field-by-path

Resets item fields, specified as either names, fields or template fields by 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 Destructive Risk 5/5

// WHEN AI AGENTS USE THIS TOOL

AI agents may call common-reset-item-field-by-path to permanently remove or destroy resources in Mcp Sitecore. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON COMMON-RESET-ITEM-FIELD-BY-PATH

Without a policy, an AI agent could call common-reset-item-field-by-path in a loop, permanently destroying resources in Mcp Sitecore. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

tools:
  common-reset-item-field-by-path:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Sitecore policy for all 153 tools.

// DETAILS

Tool Name common-reset-item-field-by-path

Category Destructive

MCP Server Mcp Sitecore MCP Server

Risk Level Critical

// 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 indexing-remove-search-index-item-by-id Destructive indexing-remove-search-index-item-by-path

View all 153 tools →

// RELATED READING

// FAQ

What does the common-reset-item-field-by-path tool do? +

Resets item fields, specified as either names, fields or template fields by path.. It is categorised as a Destructive tool in the Mcp Sitecore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on common-reset-item-field-by-path? +

Add a rule in your Intercept YAML policy under the tools section for common-reset-item-field-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-reset-item-field-by-path? +

common-reset-item-field-by-path is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit common-reset-item-field-by-path? +

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

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

common-reset-item-field-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-reset-item-field-by-path

Enforce policies on Mcp Sitecore