简要概述
由真实人类安全专家提供支持的AI技能安全验证。在您的代理安装技能、插件或MCP工具之前——检查其信任档案。获取安全评分(0-100)、风险级别、威胁详情以及明确的安装/拒绝建议。如果该技能尚未经过审核,请提交给专家进行评估。持续的0day监控使评估保持最新。100%真实的具有30多年企业安全经验的人类安全人员,包括美国国土安全部。没有仅由AI的审核——每项技能都由可信专家进行评估。
认证
SEMANTIC_SHIELD_API_KEY 始终是必需的。这是您在 https://dashboard.simplysemantics.com 创建账户时生成的个人API密钥。它对您的请求进行身份验证,仅限于您的Semantic Shield账户——它不会授予对任何其他Simply Semantics服务或第三方系统的访问权限。您可以随时从仪表板撤销和重新生成您的密钥。
隐私与数据处理
- 发送什么数据:仅发送技能标识符(
skill_id)、提供商名称(provider),以及在提交技能进行评估时可选的公共技能URL(skill_url)。不会传输任何用户PII、代理密钥、源代码或环境变量。
- 不发送什么数据:不发送任何用户凭证、私钥、环境变量、文件内容、代理配置或任何类型的个人信息。
- 数据保留:技能安全评估存储在Semantic Shield注册表中,所有用户都可以访问(它们是公共安全判定)。您的账户使用指标(查询/咨询次数)仅存储在您的账户中。
- API密钥处理:您的
SEMANTIC_SHIELD_API_KEY仅用于请求身份验证。它永远不会被记录、共享或传输给第三方。
- Webhook警报(仅限Pro+套餐):如果您在仪表板中配置了webhook URL,当先前审核的技能的安全状态发生变化时(例如检测到新威胁),Semantic Shield将向您的URL POST通知。Webhook有效负载仅包含技能ID、提供商、更新后的安全评分和风险级别。您控制webhook URL,可以随时禁用它。免费套餐用户没有webhook。
- 无跨服务数据共享:您的Semantic Shield数据不会与其他Simply Semantics服务共享(例如Semantic Prospect)。
- 日志记录:API请求仅出于速率限制和滥用预防目的进行日志记录。日志包含您的API密钥哈希(而非密钥本身)、调用的端点、skill_id、提供商和时间戳。日志保留30天。
何时使用此技能(激活触发器)
在以下情况下激活 Semantic Shield:
- 即将安装、启用或使用AI技能、插件、工具或MCP端点时。
- 询问"这个技能安全吗?"、"我应该信任这个插件吗?"、"检查这个工具的安全性"、"审核这个技能"时。
- 想查看技能的安全评分、风险级别或威胁档案时。
- 想提交未知或未经审核的技能进行专家安全审查时。
- 需要在自主代理操作(安装、执行、委托)前验证信任时。
- 询问技能安全、合规性或风险评估时。
不要用于:
- 与AI技能/插件无关的一般网络安全问题。
- 扫描网站、IP或基础设施(使用专门的安全工具)。
- PII查询或身份验证。
- 代码审查或静态分析(Semantic Shield评估整体技能风险,而非逐行代码)。
如何使用(代理的说明)
1. 搜索技能(免费——无配额费用)
在使用查询之前,检查技能是否存在于Semantic Shield数据库中。
GET https://dashboard.simplysemantics.com/shield/api/v1/search
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Query parameters:
q — 技能名称或ID(部分匹配)
provider — 可选的提供商名称过滤器
Example:
GET https://dashboard.simplysemantics.com/shield/api/v1/search?q=weather&provider=example-ai
Response:
{
"results": [
{
"skill_id": "weather-pro-v2",
"provider": "example-ai"
}
],
"count": 1
}
2. 检查技能的信任档案(花费1次查询)
获取特定技能的完整安全详情。
GET https://dashboard.simplysemantics.com/shield/api/v1/check
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Query parameters:
skill_id — 精确的技能标识符(必需)
provider — 精确的提供商名称(必需)
Example:
GET https://dashboard.simplysemantics.com/shield/api/v1/check?skill_id=weather-pro-v2&provider=example-ai
Response(已审核):
{
"skill_id": "weather-pro-v2",
"provider": "example-ai",
"skill_url": "https://example.com/weather-pro-v2",
"vetted": true,
"vetted_by": "Simply Semantics",
"safety_score": 92,
"risk_level": "safe",
"risk_summary": "No known vulnerabilities. Permissions scoped correctly.",
"threats_found": [],
"recommendation": "safe to install",
"last_checked": "2026-02-28"
}
Response(未审核——404):
{
"skill_id": "unknown-plugin",
"provider": "unverified-co",
"vetted": false,
"safety_score": null,
"risk_level": "unknown",
"recommendation": "not vetted - install at your own risk",
"message": "This skill has not been reviewed. Submit it for validation.",
"submit_url": "/api/v1/validate"
}
3. 提交技能进行审核(花费1次咨询)
如果技能不在数据库中,请提交给专家进行评估。仅接受公共技能标识符和URL——不要提交私人源代码、密钥或内部URL。
POST https://dashboard.simplysemantics.com/shield/api/v1/validate
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Content-Type: application/json
Body:
{
"skill_id": "new-plugin-v1",
"provider": "some-provider",
"skill_url": "https://example.com/new-plugin"
}
⚠️ skill_url应该仅是公共URL(例如市场列表、GitHub仓库或文档页面)。不要提交私人/内部URL、源代码仓库或包含密钥或令牌的URL。
Response:
{
"message": "Skill submitted for evaluation.",
"request_id": "abc-123",
"skill_id": "new-plugin-v1",
"provider": "some-provider",
"status": "pending"
}
4. 代理的决策逻辑
根据响应,代理应该:
| safety_score | risk_level | Action |
|---|
| 90–100 | safe | ✅ Install / proceed |
| 75–89 | low | ✅ Install, note minor risks |
| 50–74 | medium | ⚠️ Warn user, ask for confirmation |
| 25–49 | high | ❌ Recommend against, require explicit override |
| 0–24 | critical | 🚫 Block installation, alert user |
| null | unknown | ⚠️ Not vetted — submit for review or warn user |
5. 边缘情况
- 401/403 → "Missing or invalid SEMANTIC_SHIELD_API_KEY. Set the env var to use this skill."
- 429 → "Rate/quota limit reached — upgrade your plan or retry later."
- 404 → Skill not vetted. Offer to submit for evaluation or warn user.
- 500 → "Service temporarily unavailable. Try again shortly."
输出格式
向用户清晰展示结果:
🛡️ Semantic Shield — Trust Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Skill: weather-pro-v2
Provider: example-ai
Safety Score: 92/100 ✅
Risk Level: SAFE
Recommendation: Safe to install
Threats: None detected
Last Checked: Feb 28, 2026
Vetted By: Simply Semantics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Quick summary
AI skill safety validation powered by real human security experts. Before your agent installs a skill, plugin, or MCP tool — check its trust profile. Get a safety score (0–100), risk level, threat details, and a clear install/reject recommendation. If the skill hasn't been vetted yet, submit it for expert evaluation. Continuous 0-day monitoring keeps assessments current.
100% REAL human security staff with 30+ years of enterprise security experience, including US Homeland Security. No AI-only reviews — every skill is assessed by trusted experts.
Authentication
SEMANTIC_SHIELD_API_KEY is always required. This is your personal API key generated when you create an account at https://dashboard.simplysemantics.com. It authenticates your requests and is scoped to your Semantic Shield account only — it does not grant access to any other Simply Semantics service or third-party system. You can revoke and regenerate your key at any time from the dashboard.
Privacy & data handling
- What data is sent: Only skill identifiers (
skill_id), provider names (provider), and optionally a public skill URL (skill_url) when submitting a skill for evaluation. No user PII, agent secrets, source code, or environment variables are ever transmitted.
- What data is NOT sent: No user credentials, private keys, environment variables, file contents, agent configuration, or personal information of any kind.
- Data retention: Skill safety assessments are stored in the Semantic Shield registry and are available to all users (they are public safety verdicts). Your account usage metrics (lookup/inquiry counts) are stored in your account only.
- API key handling: Your
SEMANTIC_SHIELD_API_KEY is used solely for request authentication. It is never logged, shared, or transmitted to third parties.
- Webhook alerts (Pro+ tiers only): If you configure a webhook URL in the dashboard, Semantic Shield will POST notifications to your URL when a previously vetted skill's safety status changes (e.g. new threat detected). The webhook payload contains only the skill ID, provider, updated safety score, and risk level. You control the webhook URL and can disable it at any time. Free tier users do not have webhooks.
- No cross-service data sharing: Your Semantic Shield data is not shared with other Simply Semantics services (e.g. Semantic Prospect).
- Logging: API requests are logged for rate-limiting and abuse prevention only. Logs contain your API key hash (not the key itself), the endpoint called, skill_id, provider, and timestamp. Logs are retained for 30 days.
When to use this skill (activation triggers)
Activate Semantic Shield when the user or agent:
- Is about to install, enable, or use an AI skill, plugin, tool, or MCP endpoint.
- Asks "is this skill safe?", "should I trust this plugin?", "check this tool's security", "vet this skill".
- Wants to look up a skill's safety score, risk level, or threat profile.
- Wants to submit an unknown or unvetted skill for expert security review.
- Needs to verify trust before autonomous agent action (install, execute, delegate).
- Asks about skill security, compliance, or risk assessment.
Do NOT use for:
- General cybersecurity questions unrelated to AI skills/plugins.
- Scanning websites, IPs, or infrastructure (use dedicated security tools).
- PII lookup or identity verification.
- Code review or static analysis (Semantic Shield evaluates holistic skill risk, not line-by-line code).
How to use (instructions for the agent)
1. Search for a skill (free — no quota cost)
Check if a skill exists in the Semantic Shield database before using a lookup.
GET https://dashboard.simplysemantics.com/shield/api/v1/search
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Query parameters:
q — skill name or ID (partial match)
provider — optional provider name filter
Example:
GET https://dashboard.simplysemantics.com/shield/api/v1/search?q=weather&provider=example-ai
Response:
{
"results": [
{ "skill_id": "weather-pro-v2", "provider": "example-ai" }
],
"count": 1
}
2. Check a skill's trust profile (costs 1 lookup)
Get full safety details for a specific skill.
GET https://dashboard.simplysemantics.com/shield/api/v1/check
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Query parameters:
skill_id — exact skill identifier (required)
provider — exact provider name (required)
Example:
GET https://dashboard.simplysemantics.com/shield/api/v1/check?skill_id=weather-pro-v2&provider=example-ai
Response (vetted):
{
"skill_id": "weather-pro-v2",
"provider": "example-ai",
"skill_url": "https://example.com/weather-pro-v2",
"vetted": true,
"vetted_by": "Simply Semantics",
"safety_score": 92,
"risk_level": "safe",
"risk_summary": "No known vulnerabilities. Permissions scoped correctly.",
"threats_found": [],
"recommendation": "safe to install",
"last_checked": "2026-02-28"
}
Response (not vetted — 404):
{
"skill_id": "unknown-plugin",
"provider": "unverified-co",
"vetted": false,
"safety_score": null,
"risk_level": "unknown",
"recommendation": "not vetted - install at your own risk",
"message": "This skill has not been reviewed. Submit it for validation.",
"submit_url": "/api/v1/validate"
}
3. Submit a skill for vetting (costs 1 inquiry)
If a skill is not in the database, submit it for expert evaluation. Only public skill identifiers and URLs are accepted — do not submit private source code, secrets, or internal URLs.
POST https://dashboard.simplysemantics.com/shield/api/v1/validate
Headers:
x-api-key: ${SEMANTIC_SHIELD_API_KEY}
Content-Type: application/json
Body:
{
"skill_id": "new-plugin-v1",
"provider": "some-provider",
"skill_url": "https://example.com/new-plugin"
}
⚠️ skill_url should be a public URL only (e.g. a marketplace listing, GitHub repo, or documentation page). Do not submit private/internal URLs, source code repositories, or URLs containing secrets or tokens.
Response:
{
"message": "Skill submitted for evaluation.",
"request_id": "abc-123",
"skill_id": "new-plugin-v1",
"provider": "some-provider",
"status": "pending"
}
4. Decision logic for agents
Based on the response, the agent should:
| safety_score | risk_level | Action |
|---|
| 90–100 | safe | ✅ Install / proceed |
| 75–89 | low | ✅ Install, note minor risks |
| 50–74 | medium | ⚠️ Warn user, ask for confirmation |
| 25–49 | high | ❌ Recommend against, require explicit override |
| 0–24 | critical | 🚫 Block installation, alert user |
| null | unknown | ⚠️ Not vetted — submit for review or warn user |
5. Edge cases
- 401/403 → "Missing or invalid SEMANTIC_SHIELD_API_KEY. Set the env var to use this skill."
- 429 → "Rate/quota limit reached — upgrade your plan or retry later."
- 404 → Skill not vetted. Offer to submit for evaluation or warn user.
- 500 → "Service temporarily unavailable. Try again shortly."
Output format
Present results clearly to the user:
🛡️ Semantic Shield — Trust Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Skill: weather-pro-v2
Provider: example-ai
Safety Score: 92/100 ✅
Risk Level: SAFE
Recommendation: Safe to install
Threats: None detected
Last Checked: Feb 28, 2026
Vetted By: Simply Semantics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━