agent_config_drift

Confirm the tool definition change was intentional, then re-baseline trivial effort

# after reviewing the change, commit the refreshed baseline:
git add .drift-agent-config.json && git commit -m "chore: re-baseline approved MCP tool definitions"

Audit what the redefined tool did while it was trusted medium effort

Documentation →

Suppress a confirmed non-issue with a committed .pullguardignore entry (pullguard ignore locally, or comment /pullguard ignore <fingerprint> <reason> on the PR — the fingerprint is printed in the PR comment’s Triage section). Entries support expiresAt for time-boxed snoozes.

Security findings at major or critical severity — and any critical finding — always surface: .pullguardignore cannot hide them. The reviewed paths that keep them visible are acknowledged (reviewed, stays in reports) and, for a confirmed false positive, a reasoned false_positive entry — visible and audited, excluded only from the merge block.