评测大模型工具调用中的隐私泄露问题,发现任务完成不等于隐私安全。
ToolPrivacyBench: Benchmarking Purpose-Bound Privacy in Tool-Using LLM Agents

- 通过模拟业务流程,检查私密信息是否仅传递给授权工具。
- 2150个案例显示,多数任务成功执行却存在过度隐私披露。
- 适合关注AI代理隐私安全的研究者与开发者。
大型语言模型正从独立文本生成转向调用外部工具、访问环境并执行多步骤任务的智能体。然而,现有函数调用基准主要评估任务完成度和API正确性,隐私评估基准则聚焦最终输出或隐私判断,均未涵盖多工具执行轨迹中的目的性信息流动。为此,提出ToolPrivacyBench,用于审计任务私密信息是否仅流向授权工具及下游接收方,从而同时评估任务完成与隐私泄露。该基准包含2,150个案例,其中1,150个为全合成的敏感业务流程,1,000个来自现有多工具与函数调用基准。每个案例由策略知识库表示,代理在模拟业务后端上执行,评估器将记录的工具参数与后端审计日志与策略知识库比对。覆盖九种主流代理,揭示任务成功执行并不意味着隐私披露合理:代理可能在中间调用中泄露不必要的私密信息。因此,该研究提出‘需要知道’的信息披露边界,并以轨迹级审计识别多工具工作流中的隐私过披露问题。
原文摘要 · Abstract (English)
Large language models (LLMs) have increasingly moved from standalone text generation systems to agents that invoke external tools, access environments, and execute multi-step tasks. However, conventional function-calling benchmarks mainly evaluate task completion and API correctness, while privacy evaluation benchmarks typically focus on final responses or privacy judgments. Neither perspective captures purpose-bound information flow across an executed multi-tool trajectory. Motivated by this limitation in current agent evaluation, ToolPrivacyBench audits whether task-private atoms are routed only to authorized tools and downstream sinks, thereby evaluating both task completion and privacy over-disclosure during tool use. The benchmark contains 2,150 cases, including 1,150 fully synthetic privacy-sensitive business workflows and 1,000 cases adapted from existing multi-tool and function-calling benchmarks. Each case is represented by a policy knowledge base. After an agent executes against mock business backends, the evaluator compares recorded tool arguments and backend audit logs with this policy knowledge base. The evaluation covers nine widely used agents to characterize purpose-bound privacy over-disclosure. The results show that successful tool execution does not imply appropriate privacy disclosure: an agent may complete a task while transmitting unnecessary private information through intermediate tool calls. ToolPrivacyBench therefore formalizes a need-to-know disclosure boundary, under which each tool should receive only the information necessary for its stated purpose, and uses trajectory-level auditing to identify privacy over-disclosure in multi-tool workflows.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。