pbip_rename_columns · Power BI MCP Server MCP: Risk & Policy

WHAT IT DOES

What pbip_rename_columns does on Power BI MCP Server

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

WHY IT NEEDS A POLICY

Why pbip_rename_columns needs a policy

This is a Write operation because it creates or modifies data/metadata reversibly. Renaming columns updates the model schema and references throughout the project, but these changes can be undone (e.g., via version control or undo). While it affects multiple dependent objects, it does not irreversibly delete data (which would be Destructive) or execute arbitrary code (which would be Execute).

From the tool's definition Tool performs 'rename columns' which modifies data structure across TMDL files, DAX references, and report visuals. The description explicitly states it 'Updates' these artifacts, indicating reversible structural changes rather than deletion or data loss.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pbip_rename_columns Rate-limited

pbip_rename_columns 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": {
    "pbip_rename_columns": {
      "limits": [
        {
          "counter": "pbip_rename_columns_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 Power BI MCP Server, so you can run agents against it safely.

FAQ

Questions about pbip_rename_columns

What does the pbip_rename_columns tool do? +

✅ RECOMMENDED: Safely rename columns in a PBIP project. Updates TMDL files, DAX references, and report visuals. Close Power BI Desktop first, then reopen after. It is categorised as a Write tool in the Power BI 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 pbip_rename_columns? +

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

What risk level is pbip_rename_columns? +

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

Can I rate-limit pbip_rename_columns? +

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

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

pbip_rename_columns is provided by the Power BI MCP Server MCP server (sulaiman013/powerbi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.