render_look · Looker MCP Server MCP: Risk & Policy

WHAT IT DOES

What render_look does on Looker MCP Server

AI agents invoke render_look to trigger actions in Looker MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why render_look needs a policy

The name 'render_look' suggests executing a rendering operation on a Looker 'Look' (a saved query/visualization), which typically involves running a query and generating output (image, PDF, etc.). This is an Execute-level action as it triggers external computation. However, since the description is empty, confidence is reduced.

From the tool's definition Tool name 'render_look' on a server that handles Looker content management and querying; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_look Rate-limited

render_look stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "render_look": {
      "limits": [
        {
          "counter": "render_look_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 render_look

What does the render_look tool do? +

render_look. It is categorised as a Execute tool in the Looker MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on render_look? +

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

What risk level is render_look? +

render_look is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit render_look? +

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

How do I block render_look completely? +

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

What MCP server provides render_look? +

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