aem_metadata_update · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_metadata_update does on Adobe Experience Assets Dev MCP

AI agents use aem_metadata_update 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_metadata_update needs a policy

The tool modifies asset metadata within Adobe Experience Manager Assets, which is a write operation that creates or changes data. This is reversible (metadata can be updated again), so it does not qualify as Destructive. The blast radius depends on how many assets could be affected and the sensitivity of metadata being modified, hence medium severity rather than high.

From the tool's definition Tool name contains 'update' and description explicitly states 'update asset metadata in AEM Assets HTTP API'. Metadata modifications are reversible write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_metadata_update Rate-limited

aem_metadata_update 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_metadata_update": {
      "limits": [
        {
          "counter": "aem_metadata_update_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_metadata_update

What does the aem_metadata_update tool do? +

Build a request to update asset metadata 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_metadata_update? +

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

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

Can I rate-limit aem_metadata_update? +

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

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

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