Analyze historical Livy execution patterns with trend analysis and performance insights
AI agents call analyze-livy-execution-history to retrieve information from Fabric-Analytics-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes historical execution patterns and performance metrics from Livy sessions. The action verbs 'analyze' and the focus on 'historical' patterns indicate data retrieval and reporting rather than modification, execution, or deletion. There are no side effects mentioned—no data is created, modified, deleted, or external operations triggered.
From the tool's definition The tool 'analyze-livy-execution-history' with description 'Analyze historical Livy execution patterns with trend analysis and performance insights' performs read-only analysis and retrieval of historical execution data.
Documented attack patterns abuse exactly the kind of access analyze-livy-execution-history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fabric-Analytics-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze-livy-execution-history:
{
"version": "1",
"default": "deny",
"tools": {
"analyze-livy-execution-history": {}
}
}analyze-livy-execution-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.
Analyze historical Livy execution patterns with trend analysis and performance insights. It is categorised as a Read tool in the Fabric-Analytics-MCP MCP Server, which means it retrieves data without modifying state.
Register the Fabric-Analytics- MCP server in PolicyLayer and add a rule for analyze-livy-execution-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-Analytics-MCP. Nothing to install.
analyze-livy-execution-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 analyze-livy-execution-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 analyze-livy-execution-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.
analyze-livy-execution-history is provided by the Fabric-Analytics- MCP server (santhoshravindran7/fabric-analytics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 83 Fabric-Analytics-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
83 Fabric-Analytics-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.