aem_folders_move · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_folders_move does on Adobe Experience Assets Dev MCP

AI agents use aem_folders_move 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_move needs a policy

Moving a folder modifies the organizational structure and metadata relationships within AEM Assets, but the operation is reversible—the folder and its contents can be moved back to their original location. This is a Write operation (reversible data modification) rather than Destructive (irreversible deletion).

From the tool's definition Tool description states it will 'move a folder' in AEM Assets HTTP API, which modifies the location/hierarchy of data reversibly. The sibling tool 'aem_assets_move' and 'aem_folders_move' indicate this performs folder relocation operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_folders_move Rate-limited

aem_folders_move 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_move": {
      "limits": [
        {
          "counter": "aem_folders_move_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_move

What does the aem_folders_move tool do? +

Build a request to move 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_move? +

Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_folders_move: 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_move? +

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

Can I rate-limit aem_folders_move? +

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

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

aem_folders_move 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.