BLAZLE
Start free
Back to docs

Core Concepts

Agent Sweep

Agent Sweep finds every credential that acts for your team (API keys and MCP tokens), shows who owns each one and whether it is still used, and flags the ones nobody looks after any more: a key created by someone who left, a token with write rights that only reads, a key committed to a repository. You contain them in one click and revoke them through the approval queue.

A token never outlives its owner

An MCP token acts on behalf of the member who created it. BLAZLE refuses the token as soon as that member leaves the workspace (removed by an admin or deprovisioned through SCIM), or when their role drops to the token's level or below. Assign a current member as owner to bring it back. API keys keep working when their owner leaves, because pipelines often depend on them; key managers are notified instead, and on Business and Enterprise you can have those keys quarantined automatically.

Signals

SignalSeverityWhen
Owner leftCriticalThe owner is no longer a member of the workspace.
Committed to a repositoryCriticalThe GitHub App found this exact key or token in a pull request or file.
No ownerHighNo owner is recorded (keys created before ownership was tracked).
Owner outrankedHighThe owner's role is now at or below the MCP token's role.
Over-privilegedHighAn MCP token that can change things made no change in 90 days.
UnusedMediumNot used for the chosen number of days (30 by default).
Never usedMediumCreated more than 14 days ago and never used.
Never expiresLowNo expiry date is set.

"Known, still in use" silences the medium and low signals of one identity for 90 days. It never hides a critical or high one.

Quarantine and revocation

  • Quarantine is reversible: a quarantined API key stops authenticating, a quarantined MCP token keeps working read-only. Restore brings back exactly what it had.
  • Revocation is never done directly. It is proposed to Copilot Approvals and needs a second person to approve it (four-eyes). Nothing is deleted; revoked identities stay in the audit log.
  • Every action is written to the tamper-evident audit log, and the machine-identity review is part of the compliance evidence bundle on Business and Enterprise.

Found in repositories

Every pull request the GitHub App scans is checked for BLAZLE credentials; a match is tied to the exact key or token. On Business and Enterprise, Scan repositories reads the default branch of each connected repository and lists:

  • MCP configurations (.mcp.json, .cursor/mcp.json, .vscode/mcp.json, claude_desktop_config.json and others): server names and where they point, and whether secrets are written in the file. Secret values are never stored.
  • Agent instruction files such as AGENTS.md, CLAUDE.md and .cursorrules.
  • BLAZLE credentials committed anywhere in those files.

Plans

Every plan sees every agent identity and every signal. Pro Developer adds owners, quarantine and revocation, with 50 identities included. Business adds repository scans, automatic quarantine and the evidence review, with 250 included. Above the included amount, each identity is $2 per month on your subscription. Enterprise is unlimited. An identity is any API key or MCP token that is not revoked or expired.

API

GET  /api/v1/agents/sweep?dormant_days=30
POST /api/v1/agents/{api_key|mcp_token}/{id}/owner        {"user_id": 42}
POST /api/v1/agents/{api_key|mcp_token}/{id}/acknowledge
POST /api/v1/agents/{api_key|mcp_token}/{id}/quarantine
POST /api/v1/agents/{api_key|mcp_token}/{id}/restore
POST /api/v1/agents/{api_key|mcp_token}/{id}/revoke       # proposes, four-eyes
POST /api/v1/agents/repo-scan
PUT  /api/v1/agents/settings                              {"auto_quarantine": true}
GET  /api/v1/agents/usage                                 # active, included, overage

The same actions are available to agents through the MCP Copilot tools list_orphan_agents, quarantine_agent and revoke_mcp_token.

Webhook events

When a webhook URL is set in Settings, BLAZLE sends these events, signed with your webhook secret (header X-Blazle-Signature), retried three times and kept in the dead-letter queue if your endpoint stays down.

  • agent.owner_left: a member left and still owned keys or tokens.
  • agent.credential_leaked: a BLAZLE credential was found in a repository.
  • agent.quarantined and agent.restored: from the dashboard, the API or Copilot (Copilot adds "via": "copilot").
{
  "event": "agent.quarantined",
  "organization_id": 7,
  "data": { "kind": "mcp_token", "id": 31, "by_user_id": 42 },
  "timestamp": "2026-10-17T08:00:00Z"
}