desktop_connect · Power BI MCP Server MCP: Risk & Policy

WHAT IT DOES

What desktop_connect does on Power BI MCP Server

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

This tool initiates a connection to an external Power BI Desktop process, which is an active external operation beyond simple data retrieval. It triggers a network/IPC connection to a running application instance and can alter the session state (e.g., applying an RLS role for testing). This makes it Execute rather than Read, as it establishes an interactive session with side effects on the target process.

From the tool's definition Connect to a Power BI Desktop instance by port number. Optionally specify an RLS role to test.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

desktop_connect Rate-limited

desktop_connect 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_connect": {
      "limits": [
        {
          "counter": "desktop_connect_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_connect

What does the desktop_connect tool do? +

Connect to a Power BI Desktop instance by port number. Optionally specify an RLS role to test. 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_connect? +

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

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

Can I rate-limit desktop_connect? +

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

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

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