High Risk

indexing-stop-search-index

Stop one or more Sitecore search indexes. If no name is provided, all running indexes will be stopped.

Part of the Mcp Sitecore MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke indexing-stop-search-index to trigger processes or run actions in Mcp Sitecore. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

indexing-stop-search-index can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-antonytm-mcp-sitecore-server.yaml
tools:
  indexing-stop-search-index:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mcp Sitecore policy for all 153 tools.

Tool Name indexing-stop-search-index
Category Execute
Risk Level High

View all 153 tools →

What does the indexing-stop-search-index tool do? +

Stop one or more Sitecore search indexes. If no name is provided, all running indexes will be stopped.. It is categorised as a Execute tool in the Mcp Sitecore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on indexing-stop-search-index? +

Add a rule in your Intercept YAML policy under the tools section for indexing-stop-search-index. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sitecore MCP server.

What risk level is indexing-stop-search-index? +

indexing-stop-search-index is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit indexing-stop-search-index? +

Yes. Add a rate_limit block to the indexing-stop-search-index rule in your Intercept 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-stop-search-index completely? +

Set action: deny in the Intercept policy for indexing-stop-search-index. 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-stop-search-index? +

indexing-stop-search-index is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Sitecore

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.