Security Simulated 3 MCP tools

Security Engine

Secret scanning simulation and secure deploy cues.

How you use it

Always security_enforce before commit on paths that may hold credentials. Couple with hooks so raw commits cannot skip the scan.

Token savings

One prevented leak avoids rotation drills, customer trust fires, and multi-agent cleanup.

Consistency

Secret scanning and secure-deploy cues apply uniformly — no “just this once” exceptions in the enforce path.

In action

Security
Scan

Diff scanned for secrets / unsafe patterns.

Hit
Hold
Remediate

Interactive demo

Security scan Idle
  • src/config.ts: API_KEY = "sk-live-***"
  • README.md: no secrets
  • .env.example: PLACEHOLDER only

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# MCP: security_enforce
{}

# On hit: remove secret from tree, rotate provider key,
# then re-run security_enforce before commit_checkpoint.
Docs →
  • security_get
  • security_scan
  • security_enforce