Critical Risk →

session_destroy

Close and clean up a browser session. Frees a pool slot.

Part of the Leapfrog server.

session_destroy can permanently delete data in Leapfrog, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LEAPFROG →

Free to start. No card required.

AI agents may call session_destroy to permanently remove or destroy resources in Leapfrog. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call session_destroy in a loop, permanently destroying resources in Leapfrog. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "session_destroy"
  ]
}

See the full Leapfrog policy for all 37 tools.

Get this rule live on your own Leapfrog server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LEAPFROG →

View all 37 tools →

These attack patterns abuse exactly the kind of access session_destroy gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so session_destroy only ever does what you allow.

SECURE LEAPFROG →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the session_destroy tool do? +

Close and clean up a browser session. Frees a pool slot.. It is categorised as a Destructive tool in the Leapfrog 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 session_destroy? +

Register the Leapfrog MCP server in PolicyLayer and add a rule for session_destroy: 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 Leapfrog. Nothing to install.

What risk level is session_destroy? +

session_destroy 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 session_destroy? +

Yes. Add a rate_limit block to the session_destroy 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 session_destroy completely? +

Set action: deny in the PolicyLayer policy for session_destroy. 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 session_destroy? +

session_destroy is provided by the Leapfrog MCP server (leapfrog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Leapfrog tool call.

Deterministic rules across all 37 Leapfrog tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.