// SCAN REPORT

Adobe Experience Assets Dev MCP

38 tools. 18 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

18 can modify or destroy data
20 read-only
38 tools total

Community server · catalogue entry verified 02/07/2026

How to control Adobe Experience Assets Dev MCP ↓

TOOL MAP

What Adobe Experience Assets Dev MCP exposes to your agents

Read (20) Write / Execute (15) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
Critical Risk

The most dangerous Adobe Experience Assets Dev MCP tools

Destructive · High aem_assets_delete Deletion of assets in a digital asset management system is irreversible and cannot be undone. Destructive · High aem_folders_delete Folder deletion in a digital asset management system is a destructive action that cannot be undone. Destructive · High aem_renditions_delete This tool performs an irreversible deletion operation on asset renditions in Adobe Experience Manager. Write · Medium aem_reset_context This tool modifies session-level configuration by resetting integration defaults.

18 of Adobe Experience Assets Dev MCP's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Adobe Experience Assets Dev MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Adobe Experience Assets Dev MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "aem_assets_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "aem_assets_copy": {
    "limits": [
      {
        "counter": "aem_assets_copy_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "aem_assets_get": {
    "limits": [
      {
        "counter": "aem_assets_get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Adobe Experience Assets Dev MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ADOBE EXPERIENCE ASSETS DEV →

Instant setup, no code required.

FULL CATALOGUE

All 38 Adobe Experience Assets Dev MCP tools

DESTRUCTIVE 3 tools
Destructive aem_assets_delete Build a request to delete an asset in AEM Assets HTTP API. Destructive aem_folders_delete Build a request to delete a folder tree in AEM Assets HTTP API. Destructive aem_renditions_delete Build a request to delete a rendition in AEM Assets HTTP API.
WRITE 15 tools
Write aem_assets_copy Build a request to copy an asset in AEM Assets HTTP API. Write aem_assets_move Build a request to move an asset in AEM Assets HTTP API. Write aem_folders_copy Build a request to copy a folder in AEM Assets HTTP API. Write aem_folders_create Build a request to create a folder in AEM Assets HTTP API. Write aem_folders_move Build a request to move a folder in AEM Assets HTTP API. Write aem_metadata_build_sync_manifest Build a metadata sync manifest for many assets. Returns ready-to-execute per-asset PUT requests. Write aem_metadata_update Build a request to update asset metadata in AEM Assets HTTP API. Write aem_plan_efficient_upload_metadata_sync Return an efficiency-first staged plan for upload + metadata pipelines, with concurrency and retry guidance. Write aem_renditions_create Build a request to create an asset rendition in AEM Assets HTTP API. Write aem_renditions_update Build a request to update/replace an existing rendition in AEM Assets HTTP API. Write aem_reset_context Reset session-level AEM integration defaults to safe baseline values. Write aem_set_context Set session-level AEM integration defaults to improve routing and request blueprint accuracy across tools. Write aem_upload_complete Build the direct binary upload complete request for AEM as a Cloud Service. Call this after all bytes are uplo Write aem_upload_initiate Build the direct binary upload initiate request for AEM as a Cloud Service. Use this before uploading file byt Write aem_upload_plan_parts Plan binary part boundaries for direct upload using fileSize, minPartSize, and maxPartSize from initiate uploa
READ 20 tools
Read aem_assets_get Build a request to retrieve a single asset representation from AEM Assets HTTP API. Read aem_explain_auth Explain authentication and headers commonly required for AEM Assets API integrations. Read aem_explain_error_handling Explain common AEM Assets integration errors and practical retry/mitigation guidance. Read aem_explain_hierarchy_data_access Explain fast data retrieval strategies for deeply nested DAM folder hierarchies, and when to use Query Builder Read aem_explain_implementation_playbook Provide an end-to-end implementation playbook for AEM integrations (search, upload, metadata sync, renditions, Read aem_explain_metadata_sync Explain robust metadata synchronization strategy for AEM Assets integrations. Read aem_explain_pagination Explain practical pagination for Query Builder APIs, including p.limit/p.offset loops and p.guessTotal usage. Read aem_explain_upload_flow Explain the direct binary upload flow for AEM Assets Cloud Service with integration sequencing. Read aem_folders_list Build a request to list folder contents in AEM Assets HTTP API. Read aem_get_context Get current session-level AEM integration defaults. Read aem_get_operation_preset Return a strict, opinionated implementation preset with ordered steps, mapped MCP tools, safeguards, and anti- Read aem_list_operation_presets List strict AEM integration presets that reduce implementation guesswork: bulk_migration, nightly_delta_sync, Read aem_metadata_get Build a request to retrieve asset metadata from AEM Assets HTTP API. Read aem_search_hierarchy_fast_page Build a high-throughput Query Builder request for quickly reading assets from deep folder hierarchies with pag Read aem_search_query_builder_assets Build a Query Builder request for discovering assets (path, fulltext, metadata predicates, pagination, and sor Read aem_search_query_builder_delta_window Build a Query Builder request for incremental sync windows (find assets modified between timestamps). Read aem_validate_integration_plan Preflight validator for AEM integration plans. Checks required steps, safeguards, policy controls, unknown ste Read list_categories List available AEM Assets integration categories and whether each is currently loaded. Read load_category Load one tool category. Categories: uploads, folders, assets, metadata, search, renditions. Call this immediat Read search_aem_assets_api Hybrid search for AEM Assets operations with intent weighting, synonym expansion, and optional semantic rerank
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Nodebench 824 tools
adminautomation
UnClick 813 tools
adminautomation
Yaver 775 tools
adminautomation
Binance MCP Server 734 tools
adminautomation
Fortimanager 584 tools
adminautomation
Crow 573 tools
adminautomation
Mcp 571 tools
adminautomation
GoHighLevel MCP Server 566 tools
adminautomation
FAQ

Questions about Adobe Experience Assets Dev MCP

Can an AI agent delete data through the Adobe Experience Assets Dev MCP server? +

Yes. The Adobe Experience Assets Dev MCP server exposes 3 destructive tools including aem_assets_delete, aem_folders_delete, aem_renditions_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Adobe Experience Assets Dev MCP? +

The Adobe Experience Assets Dev MCP server has 15 write tools including aem_assets_copy, aem_assets_move, aem_folders_copy. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Adobe Experience Assets Dev MCP.

How many tools does the Adobe Experience Assets Dev MCP server expose? +

38 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Adobe Experience Assets Dev MCP? +

Register the Adobe Experience Assets Dev MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Adobe Experience Assets Dev MCP tool call.

Deterministic rules across all 38 Adobe Experience Assets Dev MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ADOBE EXPERIENCE ASSETS DEV →

Instant setup, no code required.

38 Adobe Experience Assets Dev MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Adobe Experience Assets Dev's registry record.

The record behind this page: 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.