Clean up expired serverless sessions from storage.
AI agents call cleanup_serverless_sessions to permanently remove resources in Session Buddy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cleaning up sessions from storage is an irreversible deletion operation. Expired sessions are removed/purged from the storage backend, which cannot be undone. While the sessions are 'expired' (reducing blast radius somewhat), the action itself is destructive and permanent.
From the tool's definition Clean up expired serverless sessions from storage
Attacks that exploit this kind of access
Clean up expired serverless sessions from storage. It is categorised as a Destructive tool in the Session Buddy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Session Buddy MCP server in PolicyLayer and add a rule for cleanup_serverless_sessions: 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 Session Buddy. Nothing to install.
cleanup_serverless_sessions 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 cleanup_serverless_sessions 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 cleanup_serverless_sessions. 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.
cleanup_serverless_sessions is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →