common-remove-item-version-by-path

Removes a version of a Sitecore item by path.

Server SitecoreMCP ramseur/mcp-sitecore-server
Category Destructive
Risk class Critical
Parameters 00 required

What common-remove-item-version-by-path does on SitecoreMCP

AI agents call common-remove-item-version-by-path to permanently remove resources in SitecoreMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why common-remove-item-version-by-path needs a policy

This tool permanently deletes item versions from a Sitecore content management system. Version deletion cannot be undone through normal operations and results in permanent loss of content data. While it does not delete the entire item, removal of versions is an irreversible destructive action that warrants the highest severity classification.

From the tool's definition Tool name explicitly states 'remove-item-version' and description confirms it 'Removes a version of a Sitecore item by path.' The verb 'remove' combined with the irreversible deletion of content versions indicates destructive behavior.

Questions about common-remove-item-version-by-path

What does the common-remove-item-version-by-path tool do? +

Removes a version of a Sitecore item by path. It is categorised as a Destructive tool in the SitecoreMCP 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-remove-item-version-by-path? +

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

common-remove-item-version-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-remove-item-version-by-path? +

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

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

common-remove-item-version-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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.