AI agents call search_query_history to retrieve information from PowerBI Analyst MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'search_query_history' clearly indicates a retrieval/query operation over historical data. It does not modify, delete, execute, or have financial consequences. The empty description lowers confidence slightly, but the semantic meaning of 'search' combined with server context confirms this is a Read operation. No side effects beyond data retrieval are expected.
From the tool's definition Tool name is 'search_query_history' with an empty description. Based on the context that the server maintains 'a query history log for cross-session reuse and auditability,' this tool retrieves or searches past queries from that log.
Documented attack patterns abuse exactly the kind of access search_query_history 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 search_query_history:
{
"version": "1",
"default": "deny",
"tools": {
"search_query_history": {}
}
}search_query_history 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.
search_query_history. It is categorised as a Read tool in the PowerBI Analyst MCP MCP Server, which means it retrieves data without modifying state.
Register the PowerBI Analyst MCP server in PolicyLayer and add a rule for search_query_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 Analyst MCP. Nothing to install.
search_query_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 search_query_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 search_query_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.
search_query_history 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.