AI agents call delete-tenant to permanently remove resources in Nile — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a tenant and likely all associated data from a database. Deletion is an irreversible operation with high blast radius—an AI agent misusing this could cause loss of critical multi-tenant data, customer information, or infrastructure. This unambiguously falls under Destructive category with critical severity due to the permanent nature of the action and potential scope of affected data.
From the tool's definition Tool name 'delete-tenant' combined with description 'Deletes a tenant from the specified database' directly indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete-tenant gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nile, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-tenant:
{
"version": "1",
"default": "deny",
"hide": [
"delete-tenant"
]
} delete-tenant 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.
Deletes a tenant from the specified database. It is categorised as a Destructive tool in the Nile MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nile MCP server in PolicyLayer and add a rule for delete-tenant: 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 Nile. Nothing to install.
delete-tenant 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-tenant 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-tenant. 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-tenant is provided by the Nile MCP server (@niledatabase/nile-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nile, 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.
11 Nile tools catalogued and risk-classified — across an index of 43,000+ MCP servers.