Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/alelaguard/agentguards-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/alelaguard/agentguards-plugins/agentguards)<a href="https://agentmods.dev/mcp/alelaguard/agentguards-plugins/agentguards"><img src="https://agentmods.dev/badge/mcp/alelaguard/agentguards-plugins/agentguards/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/alelaguard/agentguards-plugins/agentguards"><img src="https://agentmods.dev/badge/mcp/alelaguard/agentguards-plugins/agentguards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentguards scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"agentguards": {
"type": "http",
"url": "https://prod.agentguards.co/mcp",
"headers": {
"X-API-Key": "${AGENTGUARDS_API_KEY}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 3a3e2f1ff9cc
agentguards is an MCP server published in the GitHub repository alelaguard/agentguards-plugins (4 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
promptwall
LLM prompt injection firewall with session tracking, explainability and multilingual detection. Runs locally from the promptwall Python package.
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.
shellward
AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP. Runs locally from the shellward npm package. Needs 3 environment variables to run.
hangar
Policy enforcement plane for MCP: every tool call ends in a verdict. Self-hosted, MIT. Runs locally from the mcp-hangar Python package. Needs 1 environment variable to run.
koma-gate-mcp
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. Runs locally from the koma-gate-mcp npm package. Needs 6 environment variables to run.
ai-appsec
Evidence-backed AppSec for AI applications and agents. Powered by HAIEC. Runs locally from the ai-appsec npm package.