List all tables in a Power BI Service dataset via XMLA
AI agents call list_tables 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.
This tool retrieves metadata (table names) from a Power BI dataset without creating, modifying, or deleting any data. It is a read-only operation with minimal blast radius—at worst, an AI agent could enumerate dataset structure, which is informational only. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'list_tables' and description 'List all tables in a Power BI Service dataset' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all tables in a Power BI Service dataset via XMLA. 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 list_tables: 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.
list_tables 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 list_tables 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 list_tables. 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.
list_tables 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.