io.github.cleburn/aegis-mcp

MCPcommunity
v0.1.15io.github.cleburnUnknownUpdated 6mo agonpmGitHub

Runtime governance enforcement for AI agents. Zero token overhead.

MCP enforcement layer for the Aegis agent governance specification. Policy at the root. Enforcement at runtime. Accountability on every action. is an MCP server that validates every agent action against your files before it happens. Path permissions, content scanning, role boundaries, quality gates — all enforced at runtime with zero token overhead to the agent. The agent never loads your…

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 →
3GitHub stars
6mo agoLast update
Package
Authorio.github.cleburn
LicenseUnknown
Version0.1.15
Sourcemcp-registry
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✓ 60 resolved+ · none vulnerable
Tool surface9 tools · 3 privileged
Security scan✓ Cleanv0.1.18 · 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

9 tools · 3 privileged
Statically extracted from the published packagev0.1.18 · 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.

aegis_select_roleNo description published

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

aegis_check_permissionsNo description published

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

aegis_write_fileprivilegedNo description published

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

aegis_read_fileNo description published

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

aegis_delete_fileprivilegedNo description published

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

aegis_request_overrideNo description published

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

aegis_executeprivilegedNo description published

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

aegis_complete_taskNo description published

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

aegis_policy_summaryNo description published

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

0 of 9 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

MCP enforcement layer for the Aegis agent governance specification. Policy at the root. Enforcement at runtime. Accountability on every action. is an MCP server that validates every agent action against your files before it happens. Path permissions, content scanning, role boundaries, quality gates — all enforced at runtime with zero token overhead to the agent. The agent never loads your governance files. The MCP server reads them into its own process memory and validates silently. The agent…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

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