AI agent security checklist for developers
A practical, reviewable checklist for the controls that matter before an AI agent can touch real code, systems, or customer data.
Read the checklistLoading VibeLint...
VibeLint Blog
Practical guides on prompt injection, MCP risk, agent permissions, approvals, and action logs.
A practical, reviewable checklist for the controls that matter before an AI agent can touch real code, systems, or customer data.
Read the checklistTrace untrusted instructions from their source to the model and from model output to every execution-capable sink.
An MCP server extends what Claude Code can reach. Review identity, scopes, commands, network access, and approval behavior before connecting it.
A practical guide to the code, permission, tool-use, and MCP checks that keep fast AI-assisted development reviewable.
SAST analyzes static artifacts. Pre-write checks add a decision point before an AI agent writes risky code or executes a sensitive action.
Replace “the agent has tools” with explicit allow, block, and approval rules that check identity, action, target, environment, and impact before execution.
AI coding agents can hardcode keys, read .env files, paste tokens into chat, and commit credentials. Catch secret leaks before code lands and before agents open secret files.