aem_folders_delete

Build a request to delete a folder tree in AEM Assets HTTP API.

Server Adobe Experience Assets Dev MCP stubbedev/adobe-experience-dev-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What aem_folders_delete does on Adobe Experience Assets Dev MCP

AI agents call aem_folders_delete to permanently remove resources in Adobe Experience Assets Dev MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why aem_folders_delete needs a policy

Folder deletion in a digital asset management system is a destructive action that cannot be undone. It removes data permanently and affects all assets within the folder hierarchy. This falls squarely into the Destructive category, which takes precedence over Write operations. Severity is high because the blast radius includes loss of potentially many assets and their metadata, though not financial impact.

From the tool's definition Tool name explicitly states 'delete' and description states it will 'delete a folder tree in AEM Assets HTTP API'. Deleting a folder tree is an irreversible operation that removes multiple assets and their organizational structure.

Questions about aem_folders_delete

What does the aem_folders_delete tool do? +

Build a request to delete a folder tree in AEM Assets HTTP API. It is categorised as a Destructive tool in the Adobe Experience Assets Dev MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on aem_folders_delete? +

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

aem_folders_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit aem_folders_delete? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.