Add Armorer Guard runtime control

[armorer-labs]

Adds Armorer Guard to the tools catalogue as an open-source runtime scanner and MCP proxy.

I maintain Armorer Guard at Armorer Labs. I kept the entry bounded and evidence-led: it describes the local Rust hot-path scanner, MCP tool-call proxy use case, covered signals, maturity, and limitations rather than treating it as a complete agent-safety proof.

[natnew]

@claude Review this PR against CLAUDE.md and AGENTS.md.

Give a concise maintainer recommendation only. No edits, no contributor reply, no long summary.

[claude]

Claude finished @natnew's task in 1m 16s —— View job

---

PR #11 Review — Armorer Guard

• Load tools
• Read AGENTS.md, tools.md format, and diff
• Check for duplicates in README.md
• Form recommendation

---

Decision: Maintainer edit

Reason:

• The entry is in scope (runtime scanner and MCP proxy for agentic execution security), correctly formatted, placed in the right section, and carries no duplicate in README.md or resources/tools.md.
• The limitations and caveats block is thorough and appropriately bounded — no hype, no unsupported performance claims.
• One editorial flag: "active maintenance" in the maturity line is an unsupported maturity claim. Per description rules, it should be removed or replaced with something verifiable (e.g. "public code, MIT licence, local Rust runtime, CLI/MCP proxy interface, and benchmark documentation" already present are sufficient without the maturity assertion).
• Self-submission from the tool's own GitHub org (armorer-labs) warrants independent link verification before merge — confirm https://github.com/ArmorerLabs/Armorer-Guard is live and substantive.
• No scoresheet required for a tools entry.

Suggested maintainer edit to the maturity line (remove "and active maintenance"):

Early-stage open-source project with public code, MIT licence, local Rust runtime, CLI/MCP proxy interface, and benchmark documentation. Useful as an example of a lightweight runtime boundary control.

Suggested maintainer comment:

"Thank you — useful resource. I would accept it with a small maintainer edit to remove the unsupported maturity claim ('active maintenance') and keep the wording evidence-led. Link verification before merge."

---

[Copilot]

Pull request overview

Adds a new evidence-led entry to the tools catalogue for Armorer Guard, positioning it as a runtime boundary control relevant to agentic execution security (prompt/tool-call scanning + MCP proxy).

Changes:

• Add a new “Armorer Guard” tool entry with metadata (resource type, relevance, coverage, maturity, last-checked, limitations).
• Document its runtime scanning signals and explicitly scope limitations (not a complete agent-safety proof).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[natnew]

@armorer-labs Thank you for contributing Armorer Guard to the tools catalogue as an open-source runtime scanner and MCP proxy.