Delete a component from AEM
AI agents call deleteComponent to permanently remove resources in AEM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and cannot be undone without restore procedures. Removing components from AEM could break page functionality, require manual recovery, or impact published content. This is a destructive action with a significant blast radius if triggered incorrectly by an AI agent, warranting a 'high' severity rating.
From the tool's definition Tool name is 'deleteComponent' and description states 'Delete a component from AEM'. The verb 'delete' indicates irreversible removal of data/components from the Adobe Experience Manager system.
Attacks that exploit this kind of access
Delete a component from AEM. It is categorised as a Destructive tool in the AEM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AEM MCP Server MCP server in PolicyLayer and add a rule for deleteComponent: 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 AEM MCP Server. Nothing to install.
deleteComponent 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 deleteComponent 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 deleteComponent. 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.
deleteComponent is provided by the AEM MCP Server MCP server (udaykumarbpatel/aem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →