AI agents call get-livy-statement 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 previously executed statement results from Apache Livy (a Spark REST API service). It performs a query-like operation to fetch data/results that already exist, with no side effects, data modification, or resource deletion. The action is purely informational and non-destructive.
From the tool's definition Tool name 'get-livy-statement' and description 'Get the result of a statement execution' indicate retrieval of execution results without modification or deletion. 'Get' is explicitly a read operation.
Documented attack patterns abuse exactly the kind of access get-livy-statement 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 get-livy-statement:
{
"version": "1",
"default": "deny",
"tools": {
"get-livy-statement": {}
}
}get-livy-statement 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.
Get the result of a statement execution. 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 get-livy-statement: 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.
get-livy-statement 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-livy-statement 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-livy-statement. 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-livy-statement 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.