Pins and audit log

Pinned tool definitions

The first time Garm sees a server, it records a hash of each tool’s definition (name, description, input schema). If a server later changes a tool (a “rug pull”, usually new instructions hidden in the description), Garm removes that tool from the list the agent sees and blocks calls to it, so the changed text never reaches the model.

After reviewing the server and why its tools changed:

garm pins list
garm pins approve github   # its next session pins the tools it lists then

Audit log

Every session start, decision, label change and pinning event goes into a local SQLite log. Entries are hash-chained and signed with a per-install ed25519 key, so changing or deleting an entry breaks the chain and garm audit verify reports where. Entries hold what kind of secret was found and where, never the secret itself.

garm audit tail -n 50
garm audit verify --key "$(garm audit key)"

The log is written off the hot path. If it falls behind, Garm records how many events it dropped rather than slowing your agent down.