Execute a DAX query against a Power BI dataset (semantic model) and return the results. Use this tool to query data from Power BI semantic models using DAX (Data Analysis Expressions). The query must be a valid EVALUATE statement. Examples: - EVALUATE SUMMARIZECOLUMNS(
Part of the Powerbi server.
Free to start. No card required.
AI agents invoke execute_dax_query to trigger processes or run actions in Powerbi. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
execute_dax_query can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"execute_dax_query": {
"limits": [
{
"counter": "execute_dax_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Powerbi policy for all 8 tools.
These attack patterns abuse exactly the kind of access execute_dax_query gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Execute a DAX query against a Power BI dataset (semantic model) and return the results. Use this tool to query data from Power BI semantic models using DAX (Data Analysis Expressions). The query must be a valid EVALUATE statement. Examples: - EVALUATE SUMMARIZECOLUMNS(. It is categorised as a Execute tool in the Powerbi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Powerbi MCP server in PolicyLayer and add a rule for execute_dax_query: 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 Powerbi. Nothing to install.
execute_dax_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_dax_query 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.
Set action: deny in the PolicyLayer policy for execute_dax_query. 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.
execute_dax_query is provided by the Powerbi MCP server (asklokesh/powerbi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Powerbi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.