indexing-remove-search-index-item-by-path

Removes the item with the specified path from the search index. Supports wildcard filtering for the index name.

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

What indexing-remove-search-index-item-by-path does on SitecoreMCP

AI agents call indexing-remove-search-index-item-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 indexing-remove-search-index-item-by-path needs a policy

This tool permanently deletes search index entries and cannot be undone. While not destroying the underlying item itself, it irreversibly removes searchability and index state. This is classified as Destructive rather than Write because the operation cannot be reversed through normal means—index rebuilding would be required as remediation. The wildcard filtering capability increases risk of unintended bulk deletions.

From the tool's definition Tool name contains 'remove' and description states 'Removes the item...from the search index.' The verb 'Removes' combined with 'from the search index' indicates irreversible deletion of indexed data.

Questions about indexing-remove-search-index-item-by-path

What does the indexing-remove-search-index-item-by-path tool do? +

Removes the item with the specified path 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.

How do I enforce a policy on indexing-remove-search-index-item-by-path? +

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

indexing-remove-search-index-item-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 indexing-remove-search-index-item-by-path? +

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

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

indexing-remove-search-index-item-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.