This record as markdown: /tools/synthetic-ai-ae-mcp/delete-items.md
What delete_items does on Ae
AI agents call delete_items to permanently remove resources in Ae, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
save | boolean | — | Save the project after deleting. Defaults to false. |
confirm | boolean | Yes | Must be true to perform deletion. |
itemIds | array | — | Project item ids to delete. |
itemNames | array | — | Project item names to delete. |
timeoutMs | number | — | Process timeout in milliseconds. Defaults to 120000. |
projectPath | string | — | Optional absolute path to an .aep file to open first. |
Parameters from the server's own tool schema.
Why delete_items is rated Critical
An AI agent that decides to call delete_items doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ae is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_items, this is the rule to start with:
delete_items is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every delete_items call is checked against it from then on.
Questions about delete_items
Delete project panel items by id or name. Requires confirm: true. 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.
delete_items accepts 6 parameters: save, confirm, itemIds, itemNames, timeoutMs, projectPath. Required: confirm. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for delete_items: 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 Ae. Nothing to install.
delete_items 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 delete_items 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 delete_items. 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.
delete_items is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
Across the catalogue