analyze_query_performance · Power BI MCP Server MCP

WHAT IT DOES

What analyze_query_performance does on Power BI MCP Server

AI agents invoke analyze_query_performance 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 analyze_query_performance needs a policy

The tool executes a DAX query against a Power BI dataset. While the primary purpose is performance analysis (read-like intent), it actively runs/executes a query which may consume significant resources or expose sensitive data. The most severe applicable category is Execute, not Read, because it triggers external query execution whose effects depend on the DAX arguments provided.

From the tool's definition 'Execute a DAX query and report duration, row count, and heuristic optimization hints'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyze_query_performance Rate-limited

analyze_query_performance 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": {
    "analyze_query_performance": {
      "limits": [
        {
          "counter": "analyze_query_performance_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 analyze_query_performance

What does the analyze_query_performance tool do? +

Execute a DAX query and report duration, row count, and heuristic optimization hints. For storage-engine vs formula-engine server timings use DAX Studio. 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 analyze_query_performance? +

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

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

Can I rate-limit analyze_query_performance? +

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

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

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