Remove a single entry from the query history log.
AI agents call delete_query_log_entry to permanently remove resources in PowerBI Analyst MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes query history entries, which destroys audit trail evidence that may be needed for compliance, security investigation, or accountability. Unlike transient data, deletion of query logs cannot be undone and eliminates non-repudiation.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Remove a single entry from the query history log' — irreversible deletion of audit trail data.
Documented attack patterns abuse exactly the kind of access delete_query_log_entry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PowerBI Analyst MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_query_log_entry:
{
"version": "1",
"default": "deny",
"hide": [
"delete_query_log_entry"
]
}delete_query_log_entry disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a single entry from the query history log. It is categorised as a Destructive tool in the PowerBI Analyst MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PowerBI Analyst MCP server in PolicyLayer and add a rule for delete_query_log_entry: 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 Analyst MCP. Nothing to install.
delete_query_log_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_query_log_entry 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 delete_query_log_entry. 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.
delete_query_log_entry is provided by the PowerBI Analyst MCP server (mbrummerstedt/powerbi-analyst-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PowerBI Analyst MCP, 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.
12 PowerBI Analyst MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.