rollback_to_production
AI agents call rollback_to_production 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.
A rollback operation typically overwrites current changes with a prior state, which cannot be undone. In the context of a Looker MCP server that includes LookML editing capabilities, this likely reverts LookML or configuration changes to the production branch, destroying any current development work.
From the tool's definition Tool name 'rollback_to_production' implies reverting/overwriting current state to a previous production state, which is an irreversible overwrite of existing data/configuration.
Attacks that exploit this kind of access
rollback_to_production. 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 rollback_to_production: 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.
rollback_to_production 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 rollback_to_production 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 rollback_to_production. 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.
rollback_to_production 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 →