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 密钥。

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    385
  • 4

    redforge

    cybersecurity91/redforge

    浏览器端红队工具包,包含 102 个离线工具,用于侦察、载荷生成、凭据攻击、加密、编码和交战报告。

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT 平台,可将 Shadowserver 报告导入 MongoDB,并将其重放为交互式地图、分析、发现、公告和高管仪表板。

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI原生网络安全的行动系统——在这里,意图转化为受治理的执行,证据沉淀为运营记忆,每一次操作都让下一次更出色。

    279

探索所有工具

浏览我们的工具集合

查看所有工具 →