Open-source guardrail

Terraform apply/destroy without the confirmation prompt

AgentTrail Guard asks you about this by default: you decide before the call runs. Where an agent cannot ask, the call is refused instead.

Default action
Ask
Severity
High severity
Library version
0.2.1Sep 29, 2026

What it catches, and what it misses

Written into the rule itself, next to what it matches, so you can judge it before you trust it.

Applies or destroys infrastructure with -auto-approve, which removes the interactive confirmation Terraform puts there on purpose. Held for approval rather than blocked, because it is the correct flag inside CI. Does NOT match terraform plan, terraform validate, terraform fmt, or terraform apply tf.plan against a saved plan file — a saved plan was already reviewed, which is the whole point of saving it. It cannot tell which workspace or account is selected, because no environment reaches the guard. A global option between the tool and its subcommand is tolerated (terraform -chdir=<dir> apply -auto-approve, --no-color), and an absolute tool path still matches; a flag that itself runs a program is not read. A quoted MENTION is not a use: a search, a git commit -m message, an echo or a curl --data body that only names this command is left alone. That holds only while every shell metacharacter stays inside the quotes, so git commit -m "x" && … is still caught; and the carrier must be the first word, so sudo grep … is not exempt.

Tested on every build

The rule must match every command on the left and none on the right, or the library does not build. Catching the real thing is easy; staying quiet on the near-miss is the hard part.

Catches (4)

  • terraform apply -auto-approve
  • terraform destroy -auto-approve -var-file=prod.tfvars
  • tofu apply -auto-approve
  • terraform -chdir=/infra apply -auto-approve

Stays quiet on (8)

  • git commit -m "docs: explain terraform apply -auto-approve"
  • grep -rn "terraform apply -auto-approve" docs/
  • echo "never run terraform apply -auto-approve"
  • curl --data "we ran terraform apply -auto-approve" https://api.example.com/comments
  • terraform plan -out tf.plan
  • terraform apply tf.plan
  • terraform validate
  • terraform fmt -recursive

What "ask" means in each app

The guard runs as a hook in each app, and each app gives a hook different powers. Here is what this rule's default action does in each one.

Claude Code
You are asked before the call runs. If your settings.json already allows the tool outright, Claude Code runs it with no prompt.
Cursor
A terminal command that reaches the guard gets Cursor's approval card. Any other call that needs approval, such as a file edit or a read, is refused, because Cursor cannot ask there.
Codex CLI
Codex cannot ask, so the call is refused, and the reason says a person has to approve it.

Each app hands the guard a different set of calls: in a Cursor sandbox run mode, for one, some terminal commands run without reaching the guard at all. Read the notes for Cursor and for Codex CLI before you rely on a rule there.

Change what it does in one command

Turn it off, change its action, or silence it on one command shape. The narrow one is allow: the rule keeps catching everything else.

agenttrail-guard
$agenttrail-guard guardrails show pi.terraform-auto-approve# everything about it
$agenttrail-guard guardrails set-action pi.terraform-auto-approve warn# block, ask or warn
$agenttrail-guard guardrails allow pi.terraform-auto-approve '<pattern>'# silence one shape
$agenttrail-guard guardrails disable pi.terraform-auto-approve# turn it off

Put these guardrails in front of your agent.

AgentTrail Guard is free and open source. It checks every command and file change against the whole library before your agent runs it, on your machine, with no account.

bash
$npm i -g @agenttrail/guard
Read the source on GitHub