aem_renditions_create · Adobe Experience Assets Dev MCP

WHAT IT DOES

What aem_renditions_create does on Adobe Experience Assets Dev MCP

AI agents use aem_renditions_create 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_create needs a policy

This tool creates new renditions (derived versions of assets) in Adobe Experience Manager Assets, which is a write operation that modifies the asset state. Renditions are generated content that can be updated or deleted, making this reversible rather than destructive.

From the tool's definition Tool description states 'create an asset rendition' and is part of a server focused on 'upload, folder management, and metadata sync' operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aem_renditions_create Rate-limited

aem_renditions_create 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_create": {
      "limits": [
        {
          "counter": "aem_renditions_create_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_create

What does the aem_renditions_create tool do? +

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

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

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

Can I rate-limit aem_renditions_create? +

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

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

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

// THE FULL RECORD

aem_renditions_create is one line of Adobe Experience Assets Dev's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →