acp_bulk_delete_sessions_by_label

Delete sessions (max 3) matching label selector. DESTRUCTIVE: requires confirm=true.

Server Ambient Code Platform MCP Server jeremyeder/mcp
Category Destructive
Risk class Critical
Parameters 00 required

What acp_bulk_delete_sessions_by_label does on Ambient Code Platform MCP Server

AI agents call acp_bulk_delete_sessions_by_label to permanently remove resources in Ambient Code Platform MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why acp_bulk_delete_sessions_by_label needs a policy

This tool permanently deletes sessions without recovery options. The explicit 'DESTRUCTIVE' warning in the description, combined with the bulk operation scope and irreversible nature of deletion, places it in the Destructive category. Critical severity due to potential loss of active AI agent sessions and associated data across multiple resources in a Kubernetes platform.

From the tool's definition DESTRUCTIVE: requires confirm=true. Tool description explicitly labels this as DESTRUCTIVE. It deletes sessions (irreversible) based on label matching, affecting multiple resources (bulk operation).

Questions about acp_bulk_delete_sessions_by_label

What does the acp_bulk_delete_sessions_by_label tool do? +

Delete sessions (max 3) matching label selector. DESTRUCTIVE: requires confirm=true. It is categorised as a Destructive tool in the Ambient Code Platform MCP Server 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 acp_bulk_delete_sessions_by_label? +

Register the Ambient Code Platform MCP Server MCP server in PolicyLayer and add a rule for acp_bulk_delete_sessions_by_label: 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 Ambient Code Platform MCP Server. Nothing to install.

What risk level is acp_bulk_delete_sessions_by_label? +

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

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

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

acp_bulk_delete_sessions_by_label is provided by the Ambient Code Platform MCP Server MCP server (jeremyeder/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.