AI agents call get_dataset_details to retrieve information from MCP Server for Power BI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'get_dataset_details' is a retrieval operation with no side effects. It queries metadata about a dataset rather than creating, modifying, deleting, or executing operations. This aligns with the Read category. Severity is low because retrieving dataset metadata poses minimal risk—it does not modify data, execute code, or cause irreversible damage.
From the tool's definition Tool name 'get_dataset_details' indicates data retrieval. The server context shows this is part of a Power BI exploration suite alongside 'list_datasets_in_workspace' and 'execute_dax_query', where listing and retrieval operations are Read-category tasks.
Documented attack patterns abuse exactly the kind of access get_dataset_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Power BI, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dataset_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_dataset_details": {}
}
}get_dataset_details 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.
get_dataset_details. It is categorised as a Read tool in the MCP Server for Power BI MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Power BI MCP server in PolicyLayer and add a rule for get_dataset_details: 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 MCP Server for Power BI. Nothing to install.
get_dataset_details 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_dataset_details 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_dataset_details. 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_dataset_details is provided by the MCP Server for Power BI MCP server (mitsubishi-fuso/mcp-server-for-powerbi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Power BI, 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.
5 MCP Server for Power BI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.