Build a request to delete an asset in AEM Assets HTTP API.
AI agents call aem_assets_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.
Deletion of assets in a digital asset management system is irreversible and cannot be undone. This operation destroys data and has a high blast radius if invoked incorrectly by an AI agent (wrong asset, bulk deletion, etc.). This is the most severe category applicable and takes precedence over Write or Execute.
From the tool's definition Tool name 'aem_assets_delete' and description 'Build a request to delete an asset in AEM Assets HTTP API' explicitly indicate permanent deletion of asset data.
Attacks that exploit this kind of access
Build a request to delete an asset 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.
Register the Adobe Experience Assets Dev MCP server in PolicyLayer and add a rule for aem_assets_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.
aem_assets_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the aem_assets_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.
Set action: deny in the PolicyLayer policy for aem_assets_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.
aem_assets_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.
aem_assets_delete 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 →