Declared-vs-Enforced Agent Access Verification
Compares declared agent access against actual enforcement per identity class, with drift watch.
我該用這個嗎
品質與安全性
B
根據工具定義與協定合規性的自動化分析。
上下文成本
~177Token(工具定義)
~318 B典型回應大小
極小的注意力影響(128k 上下文的 0.14%)
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"declared-vs-enforced-agent-access-verification": {
"url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
}
}
}遠端端點
https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcpstreamable-http它能做什麼
工具清單
工具(3)
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
⚪access_probe(base_url, fixture, path, agent_token, signed)
Pre-flight declared-vs-enforced probe of one target path (one-time grant; the $0.01 x402 rail is the HTTP /probe endpoint).
輸入結構描述
{
"type": "object",
"properties": {
"base_url": {
"type": "string"
},
"fixture": {
"type": "string"
},
"path": {
"type": "string"
},
"agent_token": {
"type": "string"
},
"signed": {
"type": "boolean"
}
},
"required": [
"base_url"
]
}🟢drift_targets
List your enrolled drift-watch targets.
輸入結構描述
{
"type": "object",
"properties": {}
}⚪drift_run(target_id)
Re-probe one enrolled target now and record two-sided drift.
輸入結構描述
{
"type": "object",
"properties": {
"target_id": {
"type": "string"
}
},
"required": [
"target_id"
]
}社群
證據
近期觀測
已驗證未記錄版本3 個工具