list_request_history
AI agents call list_request_history to retrieve information from Fabric Dw Mcp Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty, the tool name strongly suggests it retrieves or enumerates request history from the Data Warehouse without side effects. This is a query/retrieval operation typical of Read category. Confidence is moderated slightly (0.72) because the empty description prevents full certainty, but the naming convention is clear.
From the tool's definition Tool name 'list_request_history' implies retrieval/querying of historical request data with no modification or deletion indicated. The verb 'list' is characteristic of Read operations that query or retrieve information.
Attacks that exploit this kind of access
list_request_history. It is categorised as a Read tool in the Fabric Dw Mcp Cli MCP Server, which means it retrieves data without modifying state.
Register the Fabric Dw Mcp Cli MCP server in PolicyLayer and add a rule for list_request_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 Fabric Dw Mcp Cli. Nothing to install.
list_request_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 list_request_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 list_request_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.
list_request_history is provided by the Fabric Dw Mcp Cli MCP server (sdebruyn/fabric-dw-mcp-cli). 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 →