tom_commit_transaction · Power BI MCP Server MCP

WHAT IT DOES

What tom_commit_transaction does on Power BI MCP Server

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

This tool commits pending modifications to a Power BI model's table object model (TOM), making changes permanent. While reversible (subsequent edits could undo changes), the immediate effect is to persist data/schema modifications across the Power BI system. This qualifies as Write rather than Execute because it specifically persists accumulated model changes rather than executing arbitrary code.

From the tool's definition Tool description explicitly states 'Commit (SaveChanges) all pending TOM model edits' and 'close the transaction'. The 'SaveChanges' action persists modifications to the Power BI model, which is a write operation that alters the state of the dataset.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tom_commit_transaction Rate-limited

tom_commit_transaction 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": {
    "tom_commit_transaction": {
      "limits": [
        {
          "counter": "tom_commit_transaction_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 tom_commit_transaction

What does the tom_commit_transaction tool do? +

Commit (SaveChanges) all pending TOM model edits made since tom_begin_transaction and close the transaction. 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 tom_commit_transaction? +

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

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

Can I rate-limit tom_commit_transaction? +

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

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

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