item-service-run-stored-query · Sitecore MCP: Risk & Policy

WHAT IT DOES

What item-service-run-stored-query does on SitecoreMCP

AI agents invoke item-service-run-stored-query 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.

WHY IT NEEDS A POLICY

Why item-service-run-stored-query needs a policy

This tool executes a stored query by ID, which is a dynamic operation whose side effects (data retrieval, modification, or deletion) depend on what the referenced query definition contains. While the tool itself does not author the query, executing an arbitrary stored query in Sitecore can modify content, trigger workflows, or delete data depending on the query definition. This makes it Execute rather than Read.

From the tool's definition Tool name contains 'run' and description states 'Run a stored Sitecore query' — the verb 'run' indicates execution of a pre-defined query whose effects depend on the query definition being referenced.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

item-service-run-stored-query Rate-limited

item-service-run-stored-query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "item-service-run-stored-query": {
      "limits": [
        {
          "counter": "item-service-run-stored-query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SitecoreMCP, so you can run agents against it safely.

FAQ

Questions about item-service-run-stored-query

What does the item-service-run-stored-query tool do? +

Run a stored Sitecore query 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.

How do I enforce a policy on item-service-run-stored-query? +

Register the Sitecore MCP server in PolicyLayer and add a rule for item-service-run-stored-query: 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 item-service-run-stored-query? +

item-service-run-stored-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit item-service-run-stored-query? +

Yes. Add a rate_limit block to the item-service-run-stored-query 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 item-service-run-stored-query completely? +

Set action: deny in the PolicyLayer policy for item-service-run-stored-query. 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 item-service-run-stored-query? +

item-service-run-stored-query 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.