get_power_query

THE RISK

Low Risk

Why get_power_query needs a policy

This tool retrieves and displays Power Query code for inspection purposes only. It has no side effects: it does not execute queries, modify data, delete resources, or commit financial transactions.

From the tool's definition Tool name and description indicate 'Display all M/Power Query code' — a retrieval operation that exposes underlying data transformation logic without modifying, executing, or deleting anything.

Documented attack patterns abuse exactly the kind of access get_power_query gives an agent:

POLICY

How to control get_power_query

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_power_query:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_power_query": {}
  }
}

get_power_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Pbixray — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pbixray tools

Read get_dax_columns get_dax_columns Read get_dax_measures get_dax_measures Read get_dax_tables View DAX calculated tables. Read get_m_parameters Display all M Parameters values. Read get_metadata Get metadata about the Power BI configuration used during model creation. Read get_model_size Get the model size in bytes. Read get_model_summary Get a comprehensive summary of the current Power BI model. Read get_relationships get_relationships

All 14 Pbixray tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_power_query

What does the get_power_query tool do? +

Display all M/Power Query code used for data transformation. It is categorised as a Read tool in the Pbixray MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_power_query? +

Register the Pbixray MCP server in PolicyLayer and add a rule for get_power_query: 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.

What risk level is get_power_query? +

get_power_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_power_query? +

Yes. Add a rate_limit block to the get_power_query 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.

How do I block get_power_query completely? +

Set action: deny in the PolicyLayer policy for get_power_query. 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.

What MCP server provides get_power_query? +

get_power_query 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.

Enforce policy on every Pbixray tool call.

Start from Pbixray, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →