Critical Risk →

delete-livy-session

Delete a Livy session

How to control delete-livy-session ↓

AI agents call delete-livy-session to permanently remove resources in Fabric-Analytics-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting a Livy session terminates an active Apache Spark session, which irreversibly destroys the session state, running computations, and any intermediate results not persisted. This cannot be undone and constitutes a destructive action.

From the tool's definition Tool name is 'delete-livy-session' and description states 'Delete a Livy session'. The verb 'delete' combined with session deletion represents an irreversible action.

Documented attack patterns abuse exactly the kind of access delete-livy-session 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 delete-livy-session:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-livy-session"
  ]
}

delete-livy-session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Fabric-Analytics-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete-livy-session tool do? +

Delete a Livy session. It is categorised as a Destructive tool in the Fabric-Analytics-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-livy-session? +

Register the Fabric-Analytics- MCP server in PolicyLayer and add a rule for delete-livy-session: 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.

What risk level is delete-livy-session? +

delete-livy-session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-livy-session? +

Yes. Add a rate_limit block to the delete-livy-session 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.

How do I block delete-livy-session completely? +

Set action: deny in the PolicyLayer policy for delete-livy-session. 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.

What MCP server provides delete-livy-session? +

delete-livy-session 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.

Enforce policy on every Fabric-Analytics-MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.