Delete a user from Looker. This action cannot be undone.
AI agents call delete_user to permanently remove resources in Looker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a user is an irreversible operation that removes access and associated configurations. While the blast radius is somewhat limited to a single user account (not organization-wide financial/infrastructure impacts), it meets the Destructive criterion due to its irreversibility.
From the tool's definition delete_user: 'Delete a user from Looker. This action cannot be undone.' The description explicitly states the action 'cannot be undone', meeting the definition of Destructive operations that irreversibly remove data or cannot be reversed.
Attacks that exploit this kind of access
Delete a user from Looker. This action cannot be undone. It is categorised as a Destructive tool in the Looker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for delete_user: 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 Looker MCP Server. Nothing to install.
delete_user 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_user 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_user. 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_user is provided by the Looker MCP Server MCP server (ultrathink-solutions/looker-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 →