Removes items permanently from the specified archive.
AI agents call common-remove-archive-item 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.
This tool permanently deletes data from an archive with no undo capability. Permanent removal is characteristic of Destructive operations. In a Sitecore CMS context, archive items may contain important historical content or deleted-but-recoverable data. Permanent removal from archive is irreversible and high-impact, warranting high severity.
From the tool's definition Tool description explicitly states 'Removes items permanently from the specified archive' — the word 'permanently' indicates irreversible deletion.
Attacks that exploit this kind of access
Removes items permanently from the specified archive. 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.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-remove-archive-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 SitecoreMCP. Nothing to install.
common-remove-archive-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 common-remove-archive-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 common-remove-archive-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.
common-remove-archive-item 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.
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 →