aem_renditions_update · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_renditions_update does on Adobe Experience Assets Dev MCP

AI agents use aem_renditions_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_renditions_update needs a policy

Updating or replacing a rendition modifies existing data in a reversible manner—the rendition can be updated again or restored. This is a classic Write category action. Severity is high because renditions are derivative assets in AEM; corrupting them could affect content delivery and user-facing experiences across web properties, though the action itself is not irreversible (data is not deleted, just replaced).

From the tool's definition Tool name contains 'update' and description explicitly states 'update/replace an existing rendition in AEM Assets HTTP API.' The sibling tools include destructive operations (aem_assets_delete) and read operations (aem_assets_get), positioning this tool as a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_renditions_update Rate-limited

aem_renditions_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_renditions_update": {
      "limits": [
        {
          "counter": "aem_renditions_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_renditions_update

What does the aem_renditions_update tool do? +

Build a request to update/replace an existing rendition 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_renditions_update? +

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

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

Can I rate-limit aem_renditions_update? +

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

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

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