Create a custom model set with specified LookML models.
AI agents use create_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.
Creating a model set is a Write operation because it adds new metadata/configuration to Looker that organizes and controls access to LookML models. While not destructive, it modifies system state reversibly and could affect role-based access control and query semantics if misconfigured.
From the tool's definition Tool creates a 'custom model set' by accepting 'specified LookML models' as input, which modifies Looker's semantic model configuration. This is a creation action that persists new configuration in the system.
Attacks that exploit this kind of access
Create a custom model set with specified LookML models. 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 create_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.
create_model_set 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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 →