set_user_roles · Looker MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_user_roles does on Looker MCP Server

AI agents use set_user_roles 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 set_user_roles needs a policy

Setting user roles modifies access control and permissions, which is a reversible write operation on user state. However, it carries high severity because incorrect role assignments can grant unintended access to sensitive data or administrative functions in Looker. The empty description lowers confidence slightly, but the tool name and server context make the classification clear.

From the tool's definition Tool name 'set_user_roles' indicates it modifies user role assignments. The server description confirms it provides 'administering users' capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_user_roles Rate-limited

set_user_roles 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": {
    "set_user_roles": {
      "limits": [
        {
          "counter": "set_user_roles_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 set_user_roles

What does the set_user_roles tool do? +

set_user_roles. 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 set_user_roles? +

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

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

Can I rate-limit set_user_roles? +

Yes. Add a rate_limit block to the set_user_roles 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 set_user_roles completely? +

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

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