io.github.logi-cmd/agent-guardrails

MCPcommunity
v0.3.3io.github.logi-cmdUnknownUpdated 6mo agonpm

Merge gates and safety checks for AI coding agents via MCP.

is a merge gate for AI-generated code. It checks that AI changes match expectations before you merge. 🎯 Scope validation — AI only touches allowed files ✅ Test verification — tests must pass 🔍 Drift detection — catches parallel abstractions, interface changes 🛡 Protected paths — critical files stay untouched 🔒 Security hygiene — warns on hardcoded secrets, unsafe patterns, sensitive file…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.logi-cmd
LicenseUnknown
Version0.3.3
Sourcemcp-registry
npmagent-guardrails
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface11 tools · none privileged
Security scan✓ Cleanv0.20.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged
Statically extracted from the published packagev0.20.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

read_repo_guardrailsNo description published

This tool published no description. Forge does not invent one.

suggest_task_contractNo description published

This tool published no description. Forge does not invent one.

start_agent_native_loopNo description published

This tool published no description. Forge does not invent one.

check_after_editNo description published

This tool published no description. Forge does not invent one.

finish_agent_native_loopNo description published

This tool published no description. Forge does not invent one.

run_guardrail_checkNo description published

This tool published no description. Forge does not invent one.

summarize_review_risksNo description published

This tool published no description. Forge does not invent one.

plan_rough_intentNo description published

This tool published no description. Forge does not invent one.

read_daemon_statusNo description published

This tool published no description. Forge does not invent one.

explain_changeNo description published

This tool published no description. Forge does not invent one.

query_archaeologyNo description published

This tool published no description. Forge does not invent one.

0 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

is a merge gate for AI-generated code. It checks that AI changes match expectations before you merge. 🎯 Scope validation — AI only touches allowed files ✅ Test verification — tests must pass 🔍 Drift detection — catches parallel abstractions, interface changes 🛡 Protected paths — critical files stay untouched 🔒 Security hygiene — warns on hardcoded secrets, unsafe patterns, sensitive file changes 📊 Trust score — 0-100 composite score with graduated verdicts 🔧 Auto-fix — Tier-1 issues fixed…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

11 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.