acp_bulk_stop_sessions

WHAT IT DOES

What acp_bulk_stop_sessions does on Ambient Code Platform MCP Server

AI agents invoke acp_bulk_stop_sessions to trigger actions in Ambient Code Platform MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why acp_bulk_stop_sessions needs a policy

This tool triggers external operations on remote Kubernetes-hosted Claude agents with effects that cannot be trivially undone without restarting them. While not destructive in the sense of deletion, stopping sessions halts active computational processes and terminates agent operations. The context of 'max 3' sessions and the emphasis on dry_run testing confirms this performs consequential actions.

From the tool's definition Stops multiple running sessions with operational side effects. The tool description explicitly states 'Stop multiple running sessions' and instructs users to 'Use dry_run=true first', indicating irreversible state changes to Kubernetes-hosted agents.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

acp_bulk_stop_sessions Rate-limited

acp_bulk_stop_sessions stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "acp_bulk_stop_sessions": {
      "limits": [
        {
          "counter": "acp_bulk_stop_sessions_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ambient Code Platform MCP Server, so you can run agents against it safely.

FAQ

Questions about acp_bulk_stop_sessions

What does the acp_bulk_stop_sessions tool do? +

Stop multiple running sessions (max 3). Requires confirm=true. Use dry_run=true first!. It is categorised as a Execute tool in the Ambient Code Platform MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on acp_bulk_stop_sessions? +

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

What risk level is acp_bulk_stop_sessions? +

acp_bulk_stop_sessions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit acp_bulk_stop_sessions? +

Yes. Add a rate_limit block to the acp_bulk_stop_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.

How do I block acp_bulk_stop_sessions completely? +

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

What MCP server provides acp_bulk_stop_sessions? +

acp_bulk_stop_sessions 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.