Removes the item with the specified ID from the search index. Supports wildcard filtering for the index name.
AI agents call indexing-remove-search-index-item-by-id 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 irreversibly deletes data from a search index. While the data may theoretically exist elsewhere in the CMS, the search index deletion cannot be undone without a full reindex, and it directly impacts discoverability and search functionality. This qualifies as Destructive rather than Write because the operation cannot be easily reversed and has significant consequences for system functionality.
From the tool's definition The tool 'indexing-remove-search-index-item-by-id' performs a removal operation that 'Removes the item with the specified ID from the search index.' The verb 'removes' combined with the destructive nature of deleting indexed search data indicates an…
Attacks that exploit this kind of access
Removes the item with the specified ID from the search index. Supports wildcard filtering for the index name. 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 indexing-remove-search-index-item-by-id: 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.
indexing-remove-search-index-item-by-id 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 indexing-remove-search-index-item-by-id 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 indexing-remove-search-index-item-by-id. 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.
indexing-remove-search-index-item-by-id 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 →