AI agents call item-service-delete-item to permanently remove resources in Mcp Sitecore — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a Sitecore item from the system with no undo mechanism. This is a destructive operation that cannot be reversed. While the blast radius depends on which items are targeted, deletion of critical content items, template definitions, or configuration items could cause significant system damage.
From the tool's definition 'Delete a Sitecore item by its ID' — the verb 'Delete' combined with the tool name 'delete-item' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access item-service-delete-item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Sitecore, and nothing reaches the server without passing your rules. This is the rule we recommend for item-service-delete-item:
{
"version": "1",
"default": "deny",
"hide": [
"item-service-delete-item"
]
} item-service-delete-item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a Sitecore item by its ID. 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.
Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for item-service-delete-item: 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 Mcp Sitecore. Nothing to install.
item-service-delete-item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the item-service-delete-item 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.
Set action: deny in the PolicyLayer policy for item-service-delete-item. 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.
item-service-delete-item is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Sitecore, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
149 Mcp Sitecore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.