Skip to content
KitploitKITPLOIT
ツールエクスプロイトブログ
Log in
提出
ツールエクスプロイトブログ
提出

ハッキング、侵入テスト、サイバーセキュリティツールをあなたのセキュリティアーセナルに!

Kitploitはハッキング、サイバーセキュリティ、ペネトレーションテストのツールディレクトリです。最新のプロジェクトアップデートを見つけて、脆弱性の発見、システム分析、テストの自動化、セキュリティの強化を行いましょう。

フィードお問い合わせプライバシー© 2026 Kitploit

ツールディレクトリ

カテゴリ

すべてのカテゴリを見る
Loading categories
kontext-cli — Runtime security for AI agents: discover agents, map their permissions, and enforce what they can do. | Kitploit
ツール/GitHubGitHub/kontext-security/kontext-cli
Authentication & AuthorizationCloud SecuritySecret DetectionIdentity & Access Management (IAM)Incident ResponseAI Security
GitHubkontext-security/kontext-cli

kontext-cli

Runtime security for AI agents: discover agents, map their permissions, and enforce what they can do.

リポジトリを見る
21071181日前Kitploit レビュー済み
共有
ウェブサイト
要求された言語のコンテンツは利用できません。英語版を表示しています。
Kontext animated wordmark

Website | Documentation | Dashboard | Discord

License: MIT Latest release Built with Go

Stop risky AI-agent actions before they run

AI agents do more than suggest code. They run shell commands, read files, call services, change infrastructure, and interact with production systems.

Kontext puts local policy between AI agents and the tools they call. It observes supported actions, evaluates policy before consequential actions run, and records the decision and outcome in an authorization ledger.

Start in observe mode. See what policy would stop. Move supported boundaries into enforcement when you are ready.

Policy evaluation errors, a policy that is not ready (missing, corrupt, or expired), and an unresolved identity allow the tool call, including in enforce mode, and remain visible as failures in the activity record. Only completed policy denies and unavailable required approvals block. When the hook cannot get a decision at all, because the daemon is down, restarting, too slow, or returns something unreadable, the tool call is not blocked and Kontext returns no decision, so the agent's own permission settings apply.

  • Local decisions: policy evaluation happens alongside the agent.
  • Pre-action enforcement: matching actions can be denied at supported synchronous hooks.
  • No wrapper command: install Kontext once and continue using your agents normally.
  • Attributable evidence: preserve the agent, session, action, policy decision, and outcome.
  • Managed rollout: distribute policy and review redacted records across an organization.

Kontext currently supports Claude Code, Claude Cowork, Codex, Cursor, and Antigravity. Exact event and enforcement coverage varies by agent—see the agent support matrix.

Managed Claude hooks recognize Cowork sessions with either full or shortened session directory names, preserving their Cowork identity in activity records.


Quickstart

Install Kontext

macOS

brew install --cask kontext-security/tap/kontext

The cask updates itself: the background agent checks for a new release a few minutes after it starts and every six hours, upgrades through Homebrew, and restarts on the new version. It installs the notarized binary as is, so it does not need an up-to-date Xcode.

Homebrew 7 updates only packages from taps you trust. Installing the cask by its full name trusts it. A cask installed before Homebrew 7 is not trusted, and Kontext does not trust it for you: kontext doctor shows the warning, and you run brew trust --cask kontext-security/tap/kontext once.

To let Homebrew alone manage updates, install the homebrew-core formula instead. It gets each release a few hours later, and you update it with brew upgrade kontext (Homebrew does not allow formulae to update themselves):

brew install kontext

Windows (Windows 11, x64 and Arm)

Download the zip for your PC from the latest release, unzip it into a folder you keep, and use .\kontext.exe there for the commands below. Kontext on Windows has the steps, what setup changes on the PC, and what Windows does not have yet.

Connect this machine

Create an install token in the Kontext dashboard, then run:

kontext setup

Setup:

  • stores the install token in the macOS login keychain, or in Windows Credential Manager;
  • installs hooks for supported agents in your home folder, without sudo or administrator rights;
  • starts the local Kontext daemon, and has it start when you sign in;
  • connects the installation to your Kontext organization.

Verify the installation:

kontext doctor

Then keep using Claude Code or Codex normally. You do not need to launch the agent through a separate wrapper. Codex runs hooks only after you trust them: start codex once after setup, and trust the Kontext hooks when it asks, or in /hooks.

The journey is the same on every system: install, connect with kontext setup, check with kontext doctor, keep working, and move from observing to enforcing in the dashboard. Only the install step differs.

Self-serve setup supports macOS and Windows. On Windows it covers Claude Code and Codex. Managed and cloud environments can run the same local runtime when they provide a supported hook contract, storage, and daemon lifecycle.


What changes after setup?

Without pre-action policy, an agent action executes before a security team can review its logs:

agent requests an action
        |
        v
action executes
        |
        v
activity appears in a log

With Kontext:

agent requests an action
        |
        v
Kontext receives it through a supported hook
        |
        v
local policy evaluates the action
        |
        +---- allow ----------> action continues
        |
        +---- would deny -----> action continues and evidence is recorded
        |                       (observe mode)
        |
        +---- deny -----------> action is stopped before execution
                                (enforce mode)
        |
        v
decision and outcome enter the authorization ledger

This creates a decision point before the action, not only a record after it.


Observe first. Enforce when ready.

Blocking every unfamiliar action on day one creates noise and interrupts developers. Allowing every action indefinitely leaves policy as passive monitoring.

Kontext separates rollout into two modes:

Observe mode

Observe mode records the policy decision without interrupting the agent.

Use it to answer:

  • Which tools are agents calling?
  • Which actions would current policy deny?
  • Which repositories, files, and systems are involved?
  • Where would enforcement interrupt legitimate work?
  • Which event surfaces can actually stop the action?

Enforce mode

Enforce mode returns a real denial when a deterministic policy matches at a supported synchronous pre-action hook.

Policies can define boundaries around actions such as:

  • destructive commands;
  • sensitive-file access;
  • production-system operations;
  • credential access;
  • data exports.

Enforcement is intentionally limited to event surfaces where the agent waits for Kontext before continuing. Kontext does not claim that receiving an event means it can stop every action from that agent.


Know what happened—and why

Every supported event that reaches Kontext can contribute evidence to the local authorization ledger.

A record can include:

  • the agent and session;
  • the lifecycle or tool event;
  • the tool name and available input;
  • the local policy decision;
  • the policy responsible for that decision;
  • the available action outcome;
  • redacted evidence for later review.
ツールをダウンロード

人気

すべて見る →

コミュニティで最も使われているツールを見つけましょう。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 究極のOSINTツールキット:調査グラフ、信頼度スコアリング、エイリアスファミリー、マップ、タイムライン、レポート。49個のモジュール、400以上のサイト、APIキー不要。

    717
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock ワンタップ実行アプリ(CVE-2026-43499)

    504
  • 3

    ARTEX

    baarai/artex

    プランナー/ワーカーエージェント、資産グラフと探索グラフ、MITMトラフィック記録、脆弱性の再テストを備えたLLMマルチエージェント自律ペネトレーションテストプラットフォーム。

    402
  • 4

    redforge

    cybersecurity91/redforge

    ブラウザ側のレッドチームツールキット。偵察、ペイロード生成、認証情報攻撃、暗号、エンコーディング、エンゲージメントレポート向けの102のオフラインツールを備えています。

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AIネイティブなサイバーセキュリティのためのアクションシステム。意図がガバナンスされた実行に変わり、証拠が運用記憶となり、すべての操作が次の操作を改善する。

    260
  • 6

    antifox

    antifox-ai/antifox

    偵察、攻撃対象領域の探索、エクスプロイト検証、証拠に基づくレポート提供を実行するAIマルチエージェント自律ペネトレーションテストプラットフォーム。

    259

すべてのツールを探索

ツールコレクションを閲覧

すべてのツールを見る →