add_dashboard_filter · Looker MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_dashboard_filter does on Looker MCP Server

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

Adding a filter to a dashboard creates or modifies dashboard metadata/configuration. While it affects what data is displayed, the operation is reversible (filters can be removed) and does not execute arbitrary queries, destroy data, or trigger financial transactions. This is clearly a Write operation.

From the tool's definition Tool name 'add_dashboard_filter' and description 'Add a filter to a dashboard' indicate creation/modification of dashboard configuration. This is a reversible write operation that modifies dashboard state without executing queries or deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_dashboard_filter Rate-limited

add_dashboard_filter 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": {
    "add_dashboard_filter": {
      "limits": [
        {
          "counter": "add_dashboard_filter_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 add_dashboard_filter

What does the add_dashboard_filter tool do? +

Add a filter to a dashboard. 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 add_dashboard_filter? +

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

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

Can I rate-limit add_dashboard_filter? +

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

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

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