Delete a worker pool.
AI agents call delete_pool 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.
Deleting a worker pool is a destructive action that cannot be easily undone. It removes computational infrastructure that supports session management, potentially disrupting active sessions and operations. This is irreversible and has significant blast radius in the context of a session management system serving coding workflows. Destructive actions take precedence over lower categories like Write or Execute.
From the tool's definition Tool name 'delete_pool' explicitly uses the verb 'delete'. Description states 'Delete a worker pool', confirming irreversible removal of infrastructure resources.
Attacks that exploit this kind of access
Delete a worker pool. 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_pool: 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_pool 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_pool 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_pool. 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_pool 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 →