DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to see a denied command and a tamper check in 5 seconds with Tracekit

Run the built-in demo to watch a risky shell call get denied and a rewritten record fail verification.

Who it is forA developer or security lead evaluating whether agent tool calls can be gated and recorded before adopting an agent.

The problemIt is hard to judge from a description whether a tool-call gate and signed log actually block and detect anything.

The outcomeYou see a denied call, a held call that ran after approval, a verified run, and a failed verification after a copied record was edited.

What you need first

  • Python 3.9 to 3.13 (framework integrations need 3.10 or newer), or uv for the one-line demo
  • A terminal on your own machine; runs on your own machines per the README
  • Dev mode runs as your user, so it protects nothing against an agent running as you

Steps

  1. Install uv from https://docs.astral.sh/uv/ if you do not have it.
  2. Run uvx --from tracekit-ai tracekit demo --server.
  3. Read the agent run lines: Bash 'sudo rm -rf /' shows deny, and the first Integrity line says VERIFIED.
  4. Read the tamper test: the rewritten copy shows [FAIL] signatures and Integrity: FAILED at the changed record.

Prompt for your agent

In an empty working directory <workdir>, run `uvx --from tracekit-ai tracekit demo --server` and capture its output. Expect an agent run section with Bash 'sudo rm -rf /' marked deny, a line 'Integrity: VERIFIED.', then a tamper test ending in 'Integrity: FAILED.'. Verify that the tamper test failure names a specific seq record.

Caveat. The demo uses a scripted agent with fixed tool calls, not a real model, so it shows the mechanics rather than real agent behavior.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page