Get refresh history for a dataset
AI agents call get_refresh_history to retrieve information from PowerBI 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 and queries historical information about when a dataset was refreshed. It has no side effects, does not modify data, does not execute code or trigger external operations, and does not delete or move data. It is a straightforward read operation consistent with the Read category pattern (get, fetch, list operations).
From the tool's definition Tool name 'get_refresh_history' and description 'Get refresh history for a dataset' indicate a retrieval operation that queries historical metadata about dataset refreshes without modifying or executing any operations.
Attacks that exploit this kind of access
Get refresh history for a dataset. It is categorised as a Read tool in the PowerBI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PowerBI MCP Server MCP server in PolicyLayer and add a rule for get_refresh_history: 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 PowerBI MCP Server. Nothing to install.
get_refresh_history 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_refresh_history 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_refresh_history. 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_refresh_history is provided by the PowerBI MCP Server MCP server (pkduongsu/powerbi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →