aem_assets_move · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_assets_move does on Adobe Experience Assets Dev MCP

AI agents use aem_assets_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_assets_move needs a policy

Moving an asset changes its location and potentially related metadata in the AEM Assets repository, which is a data modification operation. This is Write-category (reversible modification) rather than Destructive because moving is undoable through a reverse move operation.

From the tool's definition Tool name 'aem_assets_move' and description 'Build a request to move an asset in AEM Assets HTTP API' indicate the tool modifies asset location/metadata within the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_assets_move Rate-limited

aem_assets_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_assets_move": {
      "limits": [
        {
          "counter": "aem_assets_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_assets_move

What does the aem_assets_move tool do? +

Build a request to move an asset 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_assets_move? +

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

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

Can I rate-limit aem_assets_move? +

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

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

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