Security guardrails for AI agent payments
A watchdog MCP that validates every agent payment request against all 9 security checks before it executes — catching policy violations, replay attacks, amount tampering, revoked tokens, and budget overruns at call time. Run a pre-flight audit on any payment transaction before executing it — get PASS or BLOCKED with the specific check that failed Validate token integrity: confirms the SHA-256…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A watchdog MCP that validates every agent payment request against all 9 security checks before it executes — catching policy violations, replay attacks, amount tampering, revoked tokens, and budget overruns at call time. Run a pre-flight audit on any payment transaction before executing it — get PASS or BLOCKED with the specific check that failed Validate token integrity: confirms the SHA-256 hash matches the expected binding, catching forged or tampered tokens Enforce budget caps: rejects…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.