Tenant-wide inventory + lineage via the Admin Scanner API: workspace/dataset/report counts, datasets missing RLS or a sensitivity label, and (with dataset_name) the downstream reports that depend on a dataset across all workspaces. Requires Fabric admin (or an SP allowed to use read-only admin AP...
AI agents call cross_workspace_lineage to retrieve information from Power BI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs comprehensive data querying and discovery across tenant workspaces but does not modify, delete, execute code, or trigger financial transactions. It retrieves metadata and lineage information.
From the tool's definition Tool description states: 'Tenant-wide inventory + lineage via the Admin Scanner API' and retrieves 'workspace/dataset/report counts, datasets missing RLS or a sensitivity label, and (with dataset_name) the downstream reports that depend on a dataset across…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Tenant-wide inventory + lineage via the Admin Scanner API: workspace/dataset/report counts, datasets missing RLS or a sensitivity label, and (with dataset_name) the downstream reports that depend on a dataset across all workspaces. Requires Fabric admin (or an SP allowed to use read-only admin APIs). Cache the scan to cache_path to avoid rescanning. It is categorised as a Read tool in the Power BI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Power BI MCP Server MCP server in PolicyLayer and add a rule for cross_workspace_lineage: 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.
cross_workspace_lineage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cross_workspace_lineage 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 cross_workspace_lineage. 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.
cross_workspace_lineage 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.