View DAX calculated tables.
AI agents call get_dax_tables to retrieve information from Pbixray without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about DAX calculated tables from a PowerBI model without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—misuse would only expose existing metadata, not alter systems or data.
From the tool's definition Tool name 'get_dax_tables' and description 'View DAX calculated tables' both indicate a retrieval operation with no mutation. The verb 'View' explicitly signals read-only data access.
Documented attack patterns abuse exactly the kind of access get_dax_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pbixray, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dax_tables:
{
"version": "1",
"default": "deny",
"tools": {
"get_dax_tables": {}
}
} get_dax_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View DAX calculated tables. It is categorised as a Read tool in the Pbixray MCP Server, which means it retrieves data without modifying state.
Register the Pbixray MCP server in PolicyLayer and add a rule for get_dax_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 Pbixray. Nothing to install.
get_dax_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 get_dax_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 get_dax_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.
get_dax_tables is provided by the Pbixray MCP server (jonaolden/pbixray-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pbixray, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Pbixray tools catalogued and risk-classified — across an index of 43,000+ MCP servers.