Update a Look
AI agents use update_look to create or update resources in Looker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Looker MCP Server environment.
This tool modifies existing data/content (a Look) reversibly. It is not destructive (the Look is not deleted), not financial, and not code execution. The medium severity reflects that updating a Look could affect downstream dashboards, reports, or analyses that depend on it, potentially misleading users if the modification changes query logic or display without proper version control or change tracking.
From the tool's definition Tool name 'update_look' and description 'Update a Look' indicate modification of existing content. Looker Looks are saved queries/visualizations that can be shared and depended upon by users.
Attacks that exploit this kind of access
Update a Look. It is categorised as a Write tool in the Looker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for update_look: 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.
update_look is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_look 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 update_look. 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.
update_look 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 →