execute_dax · Power BI MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_dax does on Power BI MCP Server

AI agents invoke execute_dax to trigger actions in Power BI 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 execute_dax needs a policy

This tool runs code (DAX queries) against a live service dataset. While it may not directly delete data (which would make it Destructive), DAX queries can modify data structures, trigger cascading recalculations, and access sensitive information. The outcome depends entirely on the query provided as an argument, making it a classic Execute category risk.

From the tool's definition Tool name is 'execute_dax' and description states 'Execute a DAX query against a Power BI Service dataset'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_dax Rate-limited

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

FAQ

Questions about execute_dax

What does the execute_dax tool do? +

Execute a DAX query against a Power BI Service dataset. It is categorised as a Execute tool in the Power BI 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 execute_dax? +

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

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

Can I rate-limit execute_dax? +

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

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

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