AI agents call delete_model to permanently remove resources in SLayer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of a semantic model. While the blast radius is scoped to metadata/schema rather than the underlying data, deletion of a model could break dependent queries, dashboards, and agent workflows. The model appears to be a critical component of the SLayer abstraction layer. Destructive takes precedence over Write because the action cannot be easily reversed.
From the tool's definition Tool name is 'delete_model' and description states 'Delete a semantic model.' The verb 'delete' combined with the irreversible nature of removing a semantic model (a data structure defining how data is queried and interpreted) indicates a destructive…
Documented attack patterns abuse exactly the kind of access delete_model gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SLayer, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_model:
{
"version": "1",
"default": "deny",
"hide": [
"delete_model"
]
}delete_model 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 a semantic model. It is categorised as a Destructive tool in the SLayer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SLayer MCP server in PolicyLayer and add a rule for delete_model: 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 SLayer. Nothing to install.
delete_model 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_model 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_model. 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_model is provided by the SLayer MCP server (motleyai/slayer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SLayer, 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.
20 SLayer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.