collab_session_end

Fence future session mutations and remove the credential file. Live leases must be resolved first; incoming offers expire as an audited refusal.

SERVERAgenttool SOURCEhttps://api.agenttool.dev/v1/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-agenttool-agenttool/collab-session-end.md

WHAT IT DOES

What collab_session_end does on Agenttool

AI agents call collab_session_end to permanently remove resources in Agenttool, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why collab_session_end is rated Critical

An AI agent that decides to call collab_session_end doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Agenttool is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collab_session_end safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For collab_session_end, this is the rule to start with:

collab_session_end Hidden

collab_session_end is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "collab_session_end"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every collab_session_end call is checked against it from then on.

FAQ

Questions about collab_session_end

What does the collab_session_end tool do? +

Fence future session mutations and remove the credential file. Live leases must be resolved first; incoming offers expire as an audited refusal. It is categorised as a Destructive tool in the Agenttool 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 collab_session_end? +

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

What risk level is collab_session_end? +

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

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

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

collab_session_end is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agenttool, and thousands of servers like it.

This server

All 84 Agenttool tools → Critical-risk tools on this server →

Across the catalogue

kill_ftp_session on cPanel MCP Server →clear-session on CodeAnalysis MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →