end_session
End a specific Gemini consultation session to free up memory.
This record as markdown: /tools/namastexlabs-automagik-tools/end-session.md
What end_session does on Automagik Tools
AI agents call end_session to permanently remove resources in Automagik Tools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why end_session is rated Critical
Ending a session frees associated memory and state, which cannot be recovered once destroyed. This is an irreversible action that destroys a resource (the session), making it Destructive. However, the blast radius is limited since it only affects a single consultation session, not persistent data, hence medium severity.
From the tool's definition 'End a specific Gemini consultation session to free up memory' — terminates/destroys a session state irreversibly
Attacks that exploit this kind of access
The rule that runs end_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For end_session, this is the rule to start with:
end_session is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every end_session call is checked against it from then on.
Questions about end_session
End a specific Gemini consultation session to free up memory. It is categorised as a Destructive tool in the Automagik Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for end_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 Automagik Tools. Nothing to install.
end_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the end_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.
Set action: deny in the PolicyLayer policy for end_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.
end_session is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue