reset_datagroup
AI agents call reset_datagroup 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.
An AI agent that decides to call reset_datagroup doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Looker MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
reset_datagroup. 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 reset_datagroup: 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.
reset_datagroup 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 reset_datagroup 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 reset_datagroup. 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.
reset_datagroup 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 →