reorder_table_fields · Metabase MCP Server MCP

WHAT IT DOES

What reorder_table_fields does on Metabase MCP Server

AI agents use reorder_table_fields to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.

WHY IT NEEDS A POLICY

Why reorder_table_fields needs a policy

This tool modifies the display order/metadata of table fields, which is a reversible write operation affecting presentation configuration. It doesn't delete data or execute code, but it does alter how data is organized and displayed in Metabase, which could affect dashboards and reports relying on that field ordering.

From the tool's definition Change display order of table fields for better organization - arrange fields logically, group columns, or improve presentation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reorder_table_fields Rate-limited

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

FAQ

Questions about reorder_table_fields

What does the reorder_table_fields tool do? +

Change display order of table fields for better organization - use this to arrange fields logically, group columns, or improve presentation. It is categorised as a Write tool in the Metabase 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 reorder_table_fields? +

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

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

Can I rate-limit reorder_table_fields? +

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

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

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