Run a stored Sitecore search by its definition item ID.
AI agents invoke item-service-run-stored-search to trigger actions in SitecoreMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a stored search operation rather than simply retrieving static data. Although searches typically return read-only results, the execution of a stored search can trigger side effects depending on the search's configuration and context (e.g., logging, cache updates, or complex query operations).
From the tool's definition Tool name contains 'run' and description states 'Run a stored Sitecore search by its definition item ID'. The verb 'run' indicates execution of a predefined search operation whose effects depend on which search definition is invoked.
Attacks that exploit this kind of access
Run a stored Sitecore search by its definition item ID. It is categorised as a Execute tool in the SitecoreMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sitecore MCP server in PolicyLayer and add a rule for item-service-run-stored-search: 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.
item-service-run-stored-search is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the item-service-run-stored-search 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 item-service-run-stored-search. 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.
item-service-run-stored-search 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 →