By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Hooks as policy enforcement points

Hooks run your own code before or after agent events such as tool calls, prompts and session start. A pre-tool hook can block a command, demand extra checks, or log every action to a central system, which makes hooks a programmable layer above static rules. Deploy security hooks through managed settings so users cannot quietly remove them.

Read in this order

  1. OfficialClaude Code: Hooks referenceStart here: the event list and how a hook returns allow or deny.
  2. OfficialCursor: HooksCursor's hook events, to see how blocking semantics differ.
  3. VideoHooking Coding Agents with the Cedar Policy Language ([un]prompted 2026)Demonstrates a tool-action reference monitor built with hooks and Cedar. 17 min.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.