Inspect a .pbix file (an OPC ZIP package) without extracting: classify it as thick (imported model) vs thin (live connection), detect the report format (legacy Report/Layout vs PBIR), count pages, and list every internal entry with size. The first step to working with a real .pbix.
AI agents call pbix_inspect 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.
pbix_inspect retrieves and analyzes information about Power BI files (file structure, format type, page count, internal entries and sizes). It has no side effects—no data is created, modified, executed, or deleted. The tool is purely observational and informational, making it a Read category risk with low severity since misuse would only expose metadata about Power BI files, not cause operational harm.
From the tool's definition The tool performs inspection and analysis operations: 'classify', 'detect', 'count pages', and 'list every internal entry'. All are read-only queries that examine the structure and metadata of a .pbix file without modifying, executing, or deleting anything.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Inspect a .pbix file (an OPC ZIP package) without extracting: classify it as thick (imported model) vs thin (live connection), detect the report format (legacy Report/Layout vs PBIR), count pages, and list every internal entry with size. The first step to working with a real .pbix. 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 pbix_inspect: 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.
pbix_inspect 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 pbix_inspect 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 pbix_inspect. 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.
pbix_inspect 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.