aem_upload_complete · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_upload_complete does on Adobe Experience Assets Dev MCP

AI agents use aem_upload_complete 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_upload_complete needs a policy

This tool completes file uploads to a content management system, which creates/modifies data in a reversible manner (files can be replaced or deleted later). It is Write rather than Execute because it performs a specific data creation operation rather than arbitrary code execution.

From the tool's definition Tool is named 'aem_upload_complete' and described as building a 'direct binary upload complete request' that finalizes asset uploads to Adobe Experience Manager.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_upload_complete Rate-limited

aem_upload_complete 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_upload_complete": {
      "limits": [
        {
          "counter": "aem_upload_complete_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_upload_complete

What does the aem_upload_complete tool do? +

Build the direct binary upload complete request for AEM as a Cloud Service. Call this after all bytes are uploaded to uploadURIs. 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_upload_complete? +

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

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

Can I rate-limit aem_upload_complete? +

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

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

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