Skip to main content

Overview

The Kill Switch is an emergency mechanism to immediately terminate an agent’s access to all external services. When activated:
  1. All in-flight requests are terminated
  2. The agent’s credentials are revoked
  3. Future requests are blocked
  4. Webhooks are triggered (if configured)
Propagation time: < 100ms globally

Activation Methods

  1. Go to Agents in the dashboard
  2. Find the agent you want to kill
  3. Click the red Kill button
  4. Confirm the action
The agent status will change to “killed” and all requests will be blocked.

API

Response:

SDK (Python)

Reactivating an Agent

After investigating and resolving the issue, you can reactivate an agent:

Dashboard

  1. Go to Agents
  2. Find the killed agent (shown in red)
  3. Click Reactivate
  4. Confirm the action

API

Automatic Kill Triggers

Configure automatic kill switch activation based on:

Anomaly Detection

Rate Limiting

Injection Detection

Webhooks

Get notified when an agent is killed:
  1. Go to Activity > Webhooks
  2. Add a webhook endpoint
  3. Select the agent_killed event
Webhook Payload:

Best Practices

Monitor Before Killing

Review audit logs before killing to understand what the agent was doing

Document the Reason

Always provide a reason when killing - it helps with post-incident analysis

Set Up Webhooks

Configure webhooks to alert your team when agents are killed

Test in Staging

Test your kill switch response in staging before production incidents

FAQ

The kill switch propagates globally in under 100ms. All edge locations receive the kill signal within this time.
In-flight requests are terminated with a 503 Service Unavailable response. The client will receive an error indicating the agent has been killed.
Yes, you can reactivate an agent from the dashboard or API. However, you should investigate the reason for the kill before reactivating.
Yes, all audit logs are preserved. You can review what the agent was doing before and after the kill.