desktop_set_rls_role · Power BI MCP Server MCP

WHAT IT DOES

What desktop_set_rls_role does on Power BI MCP Server

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

This tool changes the active Row-Level Security (RLS) role, which affects how all subsequent queries are filtered. This is an Execute-level action because it modifies the runtime security context of the Power BI session, potentially allowing an AI agent to bypass or manipulate data access restrictions by switching to a different RLS role.

From the tool's definition 'Set or clear the active RLS role for testing. When set, all queries will be filtered by that role'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

desktop_set_rls_role Rate-limited

desktop_set_rls_role 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": {
    "desktop_set_rls_role": {
      "limits": [
        {
          "counter": "desktop_set_rls_role_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 desktop_set_rls_role

What does the desktop_set_rls_role tool do? +

Set or clear the active RLS role for testing. When set, all queries will be filtered by that role. 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 desktop_set_rls_role? +

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

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

Can I rate-limit desktop_set_rls_role? +

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

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

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