Get information about Sitecore search indexes. Can filter by name, database, running status, or corrupted status.
AI agents call indexing-get-search-index to retrieve information from SitecoreMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and status information about search indexes without modifying, deleting, or executing any operations. It is a straightforward read/query operation that returns information about existing system state. The low severity reflects that unauthorized access to index metadata poses minimal risk compared to data modification or destruction capabilities.
From the tool's definition Tool description states 'Get information about Sitecore search indexes' with filtering options (name, database, running status, corrupted status). The verb 'Get' and the explicit retrieval nature confirm this is a query operation with no side effects.
Attacks that exploit this kind of access
Get information about Sitecore search indexes. Can filter by name, database, running status, or corrupted status. It is categorised as a Read tool in the SitecoreMCP MCP Server, which means it retrieves data without modifying state.
Register the Sitecore MCP server in PolicyLayer and add a rule for indexing-get-search-index: 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-get-search-index is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the indexing-get-search-index 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-get-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.
indexing-get-search-index 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 →