GuardDog intercepts every exec call at the OS level and blocks any app you haven't explicitly trusted from running your AI CLI tools.
Once
claude
or any other AI CLI is installed, nothing stops a rogue script, a
malicious package, or an automated agent from calling it on your
behalf — silently, without your knowledge.
A compromised npm package or shell script can exec your AI CLI and exfiltrate context, query sensitive APIs, or drain API quota without triggering obvious alerts.
Agentic workflows can loop, branch, or escape their sandbox. Without execution controls, one badly-scoped agent can spawn thousands of unintended AI calls.
Prompt-level instructions and API keys are weak gates. They sit
outside the operating system and can be bypassed by any process
that can see your
$PATH.
GuardDog uses Apple's Endpoint Security framework to sit inline on
every
exec
syscall — before the process ever runs.
Add a CLI binary to GuardDog (e.g.
/usr/local/bin/claude) and specify exactly which
apps are allowed to call it — by bundle ID and code-signing
identity.
GuardDog's Endpoint Security extension receives an
AUTH_EXEC event before the process starts.
The kernel waits for GuardDog's verdict.
The policy engine resolves the caller's bundle ID and Team ID from its code-signing certificate — not just its path or name, which can be spoofed.
Callers on your allowlist proceed normally. Everything else is denied before a single byte of the CLI runs. The decision is logged with full context.
Blocks execute at the macOS kernel boundary using the Endpoint Security framework — the same layer used by leading EDR products.
Allowlist entries are matched on Team ID and bundle ID from the caller's code signature — not spoofable process names or paths.
Every exec attempt is logged with the target CLI, caller identity, verdict, and matched rule. Spot anomalies before they become incidents.
Trusted callers are evaluated in microseconds. GuardDog adds no measurable latency to your normal Terminal or IDE workflow.
Manage protected tools and allowlists through a clean, native macOS app — no configuration files, no CLI administration required.
GuardDog works with any executable —
claude,
openai,
gemini, or custom internal tools. No code changes needed in the
protected binary.
Once a CLI is protected, every caller not explicitly listed is blocked. You opt in to trust, not out of it.
Matching on code-signing identity means an attacker can't bypass your allowlist by renaming a binary or faking a bundle ID at runtime.
Policies are stored on-device. GuardDog never sends your rules, exec events, or identities to any external server.
GuardDog runs as an Apple-notarized system extension with the Endpoint Security entitlement — the same mechanism used by leading security vendors.
GuardDog is in early access for macOS. Join the waitlist to be notified when it's ready to install.