Gets Sitecore CLI documentation describing the most often used commands like index rebuild, item serialization, etc.
AI agents call sitecore-cli-documentation to retrieve information from Mcp Sitecore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns documentation content. There is no data modification, code execution, deletion, or financial transaction involved. It is purely informational retrieval, which falls under the 'Read' category. The severity is low because accessing documentation poses minimal risk to system integrity or security.
From the tool's definition Tool description states 'Gets Sitecore CLI documentation' — a retrieval operation with no side effects. The documentation strings for common Sitecore commands are static reference material.
Documented attack patterns abuse exactly the kind of access sitecore-cli-documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Sitecore, and nothing reaches the server without passing your rules. This is the rule we recommend for sitecore-cli-documentation:
{
"version": "1",
"default": "deny",
"tools": {
"sitecore-cli-documentation": {}
}
}sitecore-cli-documentation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets Sitecore CLI documentation describing the most often used commands like index rebuild, item serialization, etc. It is categorised as a Read tool in the Mcp Sitecore MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for sitecore-cli-documentation: 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 Mcp Sitecore. Nothing to install.
sitecore-cli-documentation 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 sitecore-cli-documentation 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 sitecore-cli-documentation. 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.
sitecore-cli-documentation is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Sitecore, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
149 Mcp Sitecore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.