aem_folders_copy · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_folders_copy does on Adobe Experience Assets Dev MCP

AI agents use aem_folders_copy to create or update resources in Adobe Experience Assets Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Experience Assets Dev MCP environment.

WHY IT NEEDS A POLICY

Why aem_folders_copy needs a policy

Copying a folder is a Write operation because it creates new data (a duplicate folder structure) without permanently destroying information. The action is reversible—the copied folder can be deleted if needed. While it modifies the asset hierarchy, it does not irreversibly delete data (ruling out Destructive) and does not execute arbitrary code or commands (ruling out Execute).

From the tool's definition The tool description states it 'Build[s] a request to copy a folder in AEM Assets HTTP API.' Copying a folder creates a new copy of the folder and its contents, which is a reversible modification to the asset hierarchy.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_folders_copy Rate-limited

aem_folders_copy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aem_folders_copy": {
      "limits": [
        {
          "counter": "aem_folders_copy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about aem_folders_copy

What does the aem_folders_copy tool do? +

Build a request to copy a folder in AEM Assets HTTP API. It is categorised as a Write tool in the Adobe Experience Assets Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on aem_folders_copy? +

Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_folders_copy: 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 Adobe Experience Assets Dev MCP. Nothing to install.

What risk level is aem_folders_copy? +

aem_folders_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit aem_folders_copy? +

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

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

aem_folders_copy is provided by the Adobe Experience Assets Dev MCP server (stubbedev/adobe-experience-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.