AI agents call delete_shell to permanently remove resources in Aas — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes Asset Administration Shells, which are core data structures in the BaSyx system. Deletion is irreversible and cannot be undone. Although the tool description is empty, the name and server context make the destructive nature clear.
From the tool's definition Tool name is 'delete_shell' combined with server description stating it performs 'full CRUD operations' on 'Asset Administration Shells' via REST API. The 'delete' prefix indicates irreversible data deletion.
Documented attack patterns abuse exactly the kind of access delete_shell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aas, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_shell:
{
"version": "1",
"default": "deny",
"hide": [
"delete_shell"
]
}delete_shell disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_shell. It is categorised as a Destructive tool in the Aas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aas MCP server in PolicyLayer and add a rule for delete_shell: 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 Aas. Nothing to install.
delete_shell 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_shell 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_shell. 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_shell is provided by the Aas MCP server (smartfactory-kl/aas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Aas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Aas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.