153 tools. 87 can modify or destroy data without limits.
24 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (common-remove-archive-item, common-remove-base-template-by-id, common-remove-base-template-by-path) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (common-add-base-template-by-id, common-add-base-template-by-path, common-add-item-version-by-id) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (common-invoke-workflow-by-id, common-invoke-workflow-by-path, common-new-item-clone-by-id) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Mcp Sitecore. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @antonytm/mcp-sitecore-server common-remove-archive-item:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
common-add-base-template-by-id:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
common-get-archive:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Mcp Sitecore server exposes 24 destructive tools including common-remove-archive-item, common-remove-base-template-by-id, common-remove-base-template-by-path. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Mcp Sitecore server has 46 write tools including common-add-base-template-by-id, common-add-base-template-by-path, common-add-item-version-by-id. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
153 tools across 4 categories: Destructive, Execute, Read, Write. 66 are read-only. 87 can modify, create, or delete data.
One line change. Instead of running the Mcp Sitecore server directly, prefix it with Intercept: intercept -c io-github-antonytm-mcp-sitecore-server.yaml -- npx -y @@antonytm/mcp-sitecore-server. Download a pre-built policy from policylayer.com/policies/io-github-antonytm-mcp-sitecore-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
See what your agent can donpx -y @policylayer/intercept