Unverified50% confidenceSolutionExact time
A safety filter that reviews only text output will miss sensitive information carried in tool-call parameters, so safety monitoring needs to be extended to the tool-call layer.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
Sources
Related Entities
Related Claims
Unverified现有文档安全扫描工具主要检查宏代码、嵌入对象和外部链接等已知威胁向量，几乎没有工具会审查空格字符的渐变色标点参数是否携带编码数据75% similarVerifiedThe trustworthiness of security tools depends greatly on transparency; only when the code is publicly auditable can the community verify its protective effectiveness.69% similarUnverifiedThe WebMCP API already provides some permission hint mechanisms, such as a read-only hint, but read-only does not equal safe—a tool that reads sensitive user information may be riskier than some write operations; for write-type tools, the criterion should be how destructive and how reversible it is, not whether it writes.68% similarUnverifiedConfiguring a check script on the "before tool call" event to block operations with exit code 2 when they hit a protected list enables gating of sensitive files, and the block applies only to the current operation rather than a permanent prohibition.68% similarUnverified开发者在处理敏感数据或依赖模型不泄露内容的场景中，应当在应用层增加额外防护，而非完全信任API层的过滤68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1100464API
curl https://kongchang.com/api/v1/knowledge/claims/1100464MCP
get_claim(id=1100464)