Low Risk

common-get-archive

Gets Sitecore database archives.

How to control common-get-archive ↓

What common-get-archive does on Mcp Sitecore

AI agents call common-get-archive 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.

Low Risk

Why common-get-archive needs a policy

This tool retrieves or queries archive data from a Sitecore database without altering, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name contains 'get' and description states 'Gets Sitecore database archives' — a retrieval operation with no modification or deletion.

Documented attack patterns abuse exactly the kind of access common-get-archive gives an agent:

How to control common-get-archive

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 common-get-archive:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "common-get-archive": {}
  }
}

common-get-archive is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Sitecore — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about common-get-archive

What does the common-get-archive tool do? +

Gets Sitecore database archives. It is categorised as a Read tool in the Mcp Sitecore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on common-get-archive? +

Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for common-get-archive: 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.

What risk level is common-get-archive? +

common-get-archive is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit common-get-archive? +

Yes. Add a rate_limit block to the common-get-archive 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 common-get-archive completely? +

Set action: deny in the PolicyLayer policy for common-get-archive. 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 common-get-archive? +

common-get-archive 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.

Enforce policy on every Mcp Sitecore tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.