Skip to content
KitploitKITPLOIT
FerramentasExploitsBlog
Log in
Enviar
FerramentasExploitsBlog
Enviar

Ferramentas de Hacking, PenTest e Cibersegurança para o seu Arsenal de Segurança!

Kitploit é um diretório de ferramentas de hacking, cibersegurança e pentesting. Descubra as últimas atualizações de projetos para encontrar vulnerabilidades, analisar sistemas, automatizar testes e fortalecer sua segurança.

FeedsContatoPrivacidade© 2026 Kitploit

Diretório de Ferramentas

Categorias

Ver todas as categorias
Loading categories
Ferramentas/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.

Ver Repositório
2107118há 15h 25mRevisado pelo Kitploit
Compartilhar
Site
Conteúdo não disponível no idioma solicitado. Mostrando versão em inglês.
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.
Baixar ferramenta

Mais Populares

Ver todos →

Descubra as ferramentas mais usadas pela nossa comunidade.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 O kit definitivo de OSINT: grafo de investigação, pontuação de confiança, famílias de alias, mapa, linha do tempo e relatórios. 49 módulos, mais de 400 sites, sem necessidade de chaves de API.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # Aplicativo de Execução em Um Toque GhostLock (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    Plataforma autônoma de testes de penetração multiagente com LLM, com agentes planejador/executor, grafos de ativos e de exploração, registro de tráfego MITM e reteste de vulnerabilidades.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Kit de ferramentas de red team do lado do navegador com 102 ferramentas offline para reconhecimento, geração de payloads, ataques a credenciais, criptografia, codificação e relatórios de engajamento.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    O sistema de ação para cibersegurança nativa em IA—onde a intenção se torna execução governada, a evidência se torna memória operacional, e cada operação melhora a próxima.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    Plataforma CSIRT que ingere relatórios do Shadowserver no MongoDB e os reproduz como mapas interativos, análises, descobertas, avisos e painéis executivos.

    256

Explore todas as ferramentas

Navegue pela nossa coleção de ferramentas

Ver todas as ferramentas →