Delete a serverless session from external storage.
AI agents call delete_serverless_session 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.
The tool permanently removes session data from external storage with no undo capability. While the blast radius is somewhat contained (only affects one session rather than data wholesale), deletion of session state could disrupt ongoing work, lose conversation history, and prevent recovery. This qualifies as Destructive rather than Write due to its irreversible nature.
From the tool's definition Tool name contains 'delete' and description states 'Delete a serverless session from external storage' — irreversible removal of data.
Attacks that exploit this kind of access
Delete a serverless session from external 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 delete_serverless_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 Session Buddy. Nothing to install.
delete_serverless_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 delete_serverless_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 delete_serverless_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.
delete_serverless_session 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 →