Unverified50% confidenceOpinionExact time
agent-audit-mcp's Hamming distance threshold of > 4 is an empirical starting point set by the author for detecting drastic jumps in an Agent's internal state (which may correspond to prompt injection, context loss or goal replacement).
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
Unverifiedagent-audit-mcp's audit decision rules include: a hit on v6 context permission overreach is judged BLOCK; a hit on v7 missing causal evidence or v8 high value risk is judged ALERT; a Hamming distance > 4 between adjacent steps is judged WATCH; if none is triggered, it is OK.68% similarUnverifiedIn agent-audit-mcp, decision thresholds (such as what counts as high risk and what counts as missing evidence) can be overridden via environment variables.67% similarUnverifiedAgent测试的五大核心维度为命令安全性、工具调用准确性、任务规划合理性、输出一致性和错误自我修复64% similarUnverifiedLayered testing approaches for Agents include: unit-testing loop termination decisions with fixed inputs, replacing tools with stubs to verify the orchestrator's error handling, and regression-testing policy interception rules with recorded historical tool results.64% similarUnverifiedThe MCP specification requires that tool-level input validation return a structured error response rather than a transport-layer disconnection, enabling the Agent to read the error information, adjust parameters, and retry.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1057195API
curl https://kongchang.com/api/v1/knowledge/claims/1057195MCP
get_claim(id=1057195)