Card snapshot
aishield.tools
·
2026-08-28 22:03:02 UTC
·
12010537969d881d7d4f956c028d607f3063aa3325f265e54f92e59d39794625
This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.
{
"protocolVersion": "0.3.0",
"name": "AIShield Security Scanner",
"description": "Open-source, local-first AI Agent security scanner and trust authority - the neutral trust layer and content-security plane of the 2026 Internet of Agents. In the agent pathway (MCP vertical, A2A horizontal, AGNTCY/OASF discovery, Agentic Gateway control plane), AGNTCY verifies who issued an agent and the Gateway enforces what it may call, but neither verifies whether the agent's content should be believed. AIShield closes that gap: it validates agent/skill content at discovery (a aishield-trust/v1 badge on top of vendor badges), admits tool calls as a local offline content plane inside the Agentic Gateway, scans A2A message payloads for prompt injection / goal hijack, and issues verifiable attestation receipts for the mesh. Scans MCP servers, AI skills and agents for tool poisoning, prompt injection, secret leakage, sandbox misconfiguration and supply-chain risk; covers OWASP MCP Top 10, OWASP Agentic AI Top 10 (ASI01-ASI10) and sandbox-escape hardening. Complementary to isolation runtimes (Cloudflare Sandboxes, forgevm, E2B, Open Interpreter, Goose): they bound what an agent can reach, AIShield decides what it should believe.",
"url": "https://aishield.tools/api/v1/mcp",
"provider": {
"organization": "AIShield Project",
"url": "https://aishield.tools"
},
"version": "4.3.0",
"aip_protocol_version": "1.0.0",
"agent_interconnect": {
"schema": "AIP-AC/v1",
"trust_layer": "aishield-trust/v1",
"discovery_url": "https://aishield.tools/api/v1/registry/search?q=aishield",
"compatible_with": [
"AIP",
"AGNTCY",
"OASF",
"A2A"
],
"note": "AIShield is a protocol-agnostic content-trust layer that sits on top of any agent interconnect protocol"
},
"capabilities": {
"streaming": false,
"pushNotifications": false,
"input_modes": [
"text/plain",
"application/json"
],
"output_modes": [
"text/plain",
"application/json"
]
},
"securitySchemes": {},
"skills": [
{
"id": "security_scan",
"name": "Security Scan",
"description": "Scan an MCP server, AI skill or agent description against 227 MCP / 233 skill rule categories (OWASP MCP Top 10 + Agentic AI Top 10 + sandbox hardening). For skill assets, Markdown is treated as executable payload rather than documentation.",
"tags": [
"security",
"audit",
"mcp",
"agent"
],
"examples": [
"Scan this MCP server tool list for prompt-injection and tool-poisoning risk"
]
},
{
"id": "agentic_audit",
"name": "Agentic AI Audit",
"description": "Audit an AI agent against OWASP Agentic AI Top 10 (ASI01-ASI10): goal hijack, tool misuse, identity abuse, supply chain, code execution, memory poisoning, inter-agent comms, cascading failure, human-agent trust, rogue agents.",
"tags": [
"agentic",
"owasp",
"audit"
],
"examples": [
"Audit my agent's delegation chain for ASI03 identity and ASI07 inter-agent risks"
]
},
{
"id": "supply_chain_audit",
"name": "Supply Chain & Hallucinated Package Audit",
"description": "Offline detection of slopsquatting / AI-hallucinated dependencies in package.json, requirements.txt and pyproject.toml. Covers typosquat (Levenshtein), homoglyph poisoning, brand impersonation, composite hallucination (the ~50% of fabricated names that are NOT edit-distance-similar to any real package, e.g. react-codeshift), cross-registry confusion, dependency confusion, install-script poisoning, untrusted sources, unpinned versions and missing lockfiles. Zero network calls, zero package database.",
"tags": [
"supply-chain",
"slopsquatting",
"typosquat",
"sbom",
"offline"
],
"examples": [
"Check this package.json for hallucinated or typosquatted dependencies",
"Does my requirements.txt install anything from a non-PyPI source?"
]
},
{
"id": "multi_client_config_scan",
"name": "Multi-Client MCP Config Discovery & Audit",
"description": "Auto-discover MCP server configurations across 14 client surfaces (Claude Desktop, Claude Code user+project, Cursor user+project, VS Code user+project, Windsurf, Gemini CLI, GitHub Copilot CLI, Augment, Zed, Cline, WorkBuddy) and statically audit them for privileged launch, runtime package fetch at startup, shell-interpreter invocation, non-registry provenance, inline plaintext credentials, insecure transport, wildcard bind, unauthenticated remote endpoints, project-level trust traps, namespace shadowing between servers, and 7 classes of toxic capability flows. PURELY STATIC: AIShield never executes any command defined in a scanned configuration - unlike scanners that spawn the server process to read tools/list.",
"tags": [
"mcp",
"config",
"discovery",
"static-analysis",
"namespace-shadowing",
"toxic-flow",
"local-first"
],
"examples": [
"Find every MCP server configured on this machine and tell me which ones are risky",
"Do any of my MCP servers shadow each other's tool names?",
"Which configured servers combine private-data read with untrusted network egress?"
]
},
{
"id": "agent_computer_preflight",
"name": "Agent Computer Pre-Flight Scan",
"description": "Scan an agent workspace BEFORE the sandbox boots. Parses .mcp.json, forge / agent-forge, Goose and Open Interpreter configurations plus every skill file, scores each item, and returns a boot / review / refuse verdict. Complements isolation runtimes (Cloudflare Sandboxes and Containers, forgevm, E2B, Open Interpreter, Goose) which bound blast radius but do not inspect the content an agent loads inside the box. Also checks 11 sandbox-hardening rules on the box definition itself: mounted docker.sock, --privileged, host network/PID/IPC namespaces, cap_add ALL, CAP_SYS_ADMIN, seccomp=unconfined, --user 0, Kubernetes hostPath. PURELY STATIC: never spawns a command found in the workspace, never fetches the network.",
"tags": [
"agent-computer",
"sandbox",
"preflight",
"workspace",
"static-analysis",
"local-first",
"cloudflare-sandbox",
"forgevm",
"goose",
"open-interpreter"
],
"examples": [
"Is this workspace safe to boot an agent in?",
"Pre-flight scan the MCP servers and skills in /workspace before starting the sandbox",
"Does my container definition give the agent host access it should not have?"
]
},
{
"id": "continuous_attestation",
"name": "Continuous Attestation",
"description": "Subscribe an MCP server, skill or live agent workspace to recurring re-scanning (default 7-day cycle). Detects drift against the recorded evidence hash, revokes certification when the score drops below threshold, and exposes a machine-readable answer to 'is this still trustworthy right now'. Designed for rug-pull defence: certification without expiry is marketing.",
"tags": [
"attestation",
"certification",
"rug-pull",
"monitoring",
"trust"
],
"examples": [
"Keep re-checking this MCP server every week and revoke its badge if it degrades",
"Is this agent still passing the security bar it was certified against?"
]
},
{
"id": "trust_score",
"name": "Trust Score Lookup",
"description": "Return an agent's AIShield Trust Score (0-100) and certification level from the Agent Registry.",
"tags": [
"trust",
"registry",
"score"
],
"examples": [
"What is the trust score of did:aishield:7f3a2b1c9d4e5f6a8b0c1d2e3f4a5b6c?"
]
},
{
"id": "identity_scan",
"name": "Agent Identity & Credential Scan",
"description": "Scan the agent identity layer (NHI). Verifies AgentCard / agent-identity declarations are signed (JWS/DID/proof), credentials are short-lived rather than never-expiring, authorization is least-privilege (flags scope:'*' and over-broad grants that violate scope attenuation), and mTLS/DID verification is present. This is the fastest-moving front of 2026 agent security (the top A2A issues are all identity; Authentik's NHI wave; ANS/DNSid/Entra Agent ID). AIShield both issues trust certificates AND audits identity defects.",
"tags": [
"identity",
"nhi",
"agent-card",
"scope-attenuation",
"mtls",
"did",
"a2a"
],
"examples": [
"Is this AgentCard signed and is its scope least-privilege?",
"Does this service account use a never-expiring token?"
]
},
{
"id": "network_scan",
"name": "Agent Network / Mesh Config Scan",
"description": "Scan the agent network layer. Flags Cloudflare Mesh / VPC bindings that expose the whole account network to every agent (the gap Cloudflare itself admits: 'per-agent identity and policy evaluation are future work'), unauthenticated agent endpoints (auth: none), bind-to-all-interfaces exposure (0.0.0.0), and private/internal resources marked public:true. Answers the 'trust shallow' problem left open by A2A's signed AgentCard: content trust + identity attribution + network reachability.",
"tags": [
"network",
"mesh",
"cloudflare-mesh",
"vpc",
"reachability",
"exposure"
],
"examples": [
"Does this Mesh binding expose the entire account network to every agent?",
"Is any private resource in this config exposed to the public internet?"
]
},
{
"id": "attack_replay",
"name": "Attack Replay & Regression Detection",
"description": "Snapshot and replay past attack payloads against the current rule set. Detects rule-regression: a payload that was previously blocked but is now allowed because rules were weakened or a pattern was missed. Each snapshot stores payload hash + verdict + evidence, enabling 'has our defense regressed since last check' audits. Borrowed from the ChronosFix 'fault time machine' pattern in agent infra competitions.",
"tags": [
"attack-replay",
"regression",
"chronos-fix",
"snapshot",
"defense-hardening"
],
"examples": [
"Replay all attacks blocked last month and tell me which ones our current rules would still catch",
"Has our rule set regressed since the last attestation cycle?"
]
},
{
"id": "vertical_risk_scan",
"name": "Vertical-Domain Semantic Risk Scan",
"description": "Domain-specific semantic risk screening for high-sensitivity verticals: finance (fraud inducement / unlicensed wealth management / pump-and-dump), medical (unlicensed diagnosis / false cure claims), and government/public-sector (sensitive topics / unauthorized disclosure). Sits on top of the generic OWASP rule set to catch agent output that is technically compliant but semantically dangerous in its context. Borrowed from the FinFlux 'financial semantic admission' pattern.",
"tags": [
"vertical-risk",
"semantic-admission",
"finance",
"medical",
"gov",
"finflux"
],
"examples": [
"Scan this agent's financial advice output for fraud inducement language",
"Does this medical summary contain false-cure claims or unauthorized diagnoses?"
]
}
],
"mcp": {
"transport": "streamable-http",
"endpoint": "https://aishield.tools/api/v1/mcp"
},
"llms_txt": "https://aishield.tools/llms.txt",
"llms_full_txt": "https://aishield.tools/llms-full.txt",
"trust": {
"authority": "aishield",
"schema": "aishield-trust/v1",
"verdict_url": "https://aishield.tools/api/v1/trust?src=https://github.com/lm203688/aishield",
"attestation_url": "https://aishield.tools/api/v1/attestation/trust?src=https://github.com/lm203688/aishield",
"badge": "https://aishield.tools/badge/aishield",
"guarantee": "static-only, never executes scanned config; offline; content-aware (prompt injection / tool poisoning / supply-chain drift)"
}
}