Critical Risk →

ae_delete_layer

Remove a layer from the composition permanently

Part of the Ae MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ae-mcp-server Destructive

AI agents may call ae_delete_layer to permanently remove or destroy resources in Ae. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call ae_delete_layer in a loop, permanently destroying resources in Ae. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

ae.yaml
tools:
  ae_delete_layer:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Ae policy for all 35 tools.

Tool Name ae_delete_layer
Category Destructive
MCP Server Ae MCP Server
Risk Level Critical

View all 35 tools →

Agents calling destructive-class tools like ae_delete_layer have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

ae_delete_layer is one of the critical-risk operations in Ae. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the ae_delete_layer tool do? +

Remove a layer from the composition permanently. It is categorised as a Destructive tool in the Ae 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 ae_delete_layer? +

Add a rule in your Intercept YAML policy under the tools section for ae_delete_layer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ae MCP server.

What risk level is ae_delete_layer? +

ae_delete_layer 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 ae_delete_layer? +

Yes. Add a rate_limit block to the ae_delete_layer rule in your Intercept 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 ae_delete_layer completely? +

Set action: deny in the Intercept policy for ae_delete_layer. 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 ae_delete_layer? +

ae_delete_layer is provided by the Ae MCP server (ae-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.