rescan_table_field_values · Metabase MCP Server MCP

WHAT IT DOES

What rescan_table_field_values does on Metabase MCP Server

AI agents invoke rescan_table_field_values to trigger actions in Metabase 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 rescan_table_field_values needs a policy

While the tool does not create, destroy, or modify actual data records, it executes a scheduled backend operation (cache refresh) whose effects depend on the current state of the table. This falls under Execute category because it triggers an external operation.

From the tool's definition Tool description states 'Trigger rescan to refresh field values cache' - the word 'trigger' indicates it executes a backend operation that has external effects (cache refresh, statistics update).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rescan_table_field_values Rate-limited

rescan_table_field_values 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": {
    "rescan_table_field_values": {
      "limits": [
        {
          "counter": "rescan_table_field_values_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 Metabase MCP Server, so you can run agents against it safely.

FAQ

Questions about rescan_table_field_values

What does the rescan_table_field_values tool do? +

Trigger rescan to refresh field values cache with current data - use this to update dropdown options, statistics, or filter values. It is categorised as a Execute tool in the Metabase 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 rescan_table_field_values? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for rescan_table_field_values: 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 Metabase MCP Server. Nothing to install.

What risk level is rescan_table_field_values? +

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

Can I rate-limit rescan_table_field_values? +

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

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

rescan_table_field_values is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.