Delete a tenant
AI agents call delete_tenant to permanently remove resources in UseGrant MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a tenant entity. Tenant deletion is a destructive operation that cannot be undone and likely affects multiple users, clients, and configurations associated with that tenant. The blast radius is substantial—an AI agent accidentally deleting the wrong tenant could eliminate an entire organization's data and access within the UseGrant platform.
From the tool's definition Tool name is 'delete_tenant' with description 'Delete a tenant'. The verb 'delete' combined with the high-impact resource 'tenant' (which typically represents an entire organizational unit or customer in multi-tenant systems) indicates irreversible data…
Attacks that exploit this kind of access
Delete a tenant. It is categorised as a Destructive tool in the UseGrant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UseGrant MCP Server 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 UseGrant MCP Server. 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 UseGrant MCP Server MCP server (usegranthq/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →