update_model_set · Looker MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_model_set does on Looker MCP Server

AI agents use update_model_set 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.

WHY IT NEEDS A POLICY

Why update_model_set needs a policy

This tool modifies an existing model set configuration in Looker, which is a reversible change. While it affects semantic model governance and could impact query behavior across dependent dashboards and reports if misused, it does not delete data, execute arbitrary code, or move financial resources. The blast radius is constrained to the model set scope and can be undone via subsequent updates.

From the tool's definition Tool name is 'update_model_set' and description states 'Update an existing model set'. The verb 'update' indicates modification of existing data rather than deletion or irreversible changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_model_set Rate-limited

update_model_set stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_model_set": {
      "limits": [
        {
          "counter": "update_model_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Looker MCP Server, so you can run agents against it safely.

FAQ

Questions about update_model_set

What does the update_model_set tool do? +

Update an existing model set. 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.

How do I enforce a policy on update_model_set? +

Register the Looker MCP Server MCP server in PolicyLayer and add a rule for update_model_set: 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.

What risk level is update_model_set? +

update_model_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_model_set? +

Yes. Add a rate_limit block to the update_model_set 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.

How do I block update_model_set completely? +

Set action: deny in the PolicyLayer policy for update_model_set. 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.

What MCP server provides update_model_set? +

update_model_set 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.