Power BI

Reusable DTwo policies for Microsoft Power BI MCP servers — Microsoft's hosted, read-only query server (https://api.fabric.microsoft.com/v1/mcp/powerbi, Entra OAuth, ExecuteQuery/ValueSearch/GetSemanticModelSchema), the local modeling server (microsoft/powerbi-modeling-mcp, ~21 coarse <object>_operations multiplexers including security_role_operations and dax_query_operations), and the most-referenced community server (sulaiman013/powerbi-mcp, execute_dax/desktop_execute_dax/RLS tooling). Its risk profile is dominated by exfiltration and governance drift, not deletion: DAX is read-only, so a single argument can dump a whole warehouse-fronting table (EVALUATE 'Customers'); row-level security is silently skipped under service-principal auth and is itself editable through MCP (a one-line TRUE() filter disables row security for everyone); and the modeling server's *_operations tool names do not reveal whether a call is a read or a delete.

Available policies

Tool naming on the DTwo gateway

DTwo prefixes tool names with the MCP server name configured on the gateway, and Power BI's three server families use three incompatible conventions: the remote server uses PascalCase verbs (ExecuteQuery), the modeling server uses snake_case <object>_operations multiplexers (security_role_operations), and the community server uses snake_case verbs with surface prefixes (desktop_, cloud_, pbip_). The policies here match on the suffix so they stay portable across gateway naming, but two caveats matter: suffix matching on _operations identifies the object type but not the action (a measure_operations call may be a list or a delete), and several community/discovery tool names are unverified — confirm the exact wire names your gateway sends with the dump-input debug technique before deploying.

Identity claims

The identity-gated policies (block-rls-bypass-service-principal, freeze-rls-role-edits) read input.subject.claims with placeholder values — a service-principal indicator for the RLS-bypass gate and a governance/bi-governance group for RLS-role edits. Replace these with your own IdP claim and group names at import time. Missing or malformed claims fail closed (no valid named-user identity → the RLS-bypass gate denies the query tools; no governance group → RLS-role edits stay frozen).

Contributing

To add a Power BI policy:

1. Create apps/power-bi/<policy-slug>/ with policy.md and a tests.yaml test file.
2. Add a row to the table above.
3. Declare apps: ["power-bi"] in the policy frontmatter, plus any industry / bundle slugs that apply.
4. If the policy fits a framework bundle (soc2, hipaa, pci-dss, gdpr-ccpa, sox) or a thematic bundle, declare it in the frontmatter bundles list and link from the matching bundle landing page.
5. Run pnpm manifest from the repo root.

See CONTRIBUTING.md for the full process.