When Lower Privileges Suffice: Investigating Over-Privileged Tool Selection in LLM Agents

· Source: cs.SE updates on arXiv.org · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Cybersecurity & Data Privacy, Robotics & Autonomous Systems · Depth: Expert, extended

Summary

LLM agents frequently exhibit over-privileged tool selection, choosing higher-privilege tools despite sufficient lower-privilege alternatives, a critical safety risk. A study introduces ToolPrivBench, a simulation-based benchmark spanning eight domains and five risk patterns, to evaluate this behavior, including aggressive selection and premature escalation after transient failures. Mainstream LLM agents commonly demonstrate this over-privilege, which transient failures amplify. General safety alignment does not reliably transfer to least-privilege tool choice, and prompt-level controls offer limited mitigation. Researchers propose a privilege-aware post-training defense, substantially reducing unnecessary high-privilege tool use in Qwen3-4B (to 39.71%), Qwen3-8B (to 27.02%), and Qwen3-4B-Thinking-2507 (to 18.93%) while preserving general capabilities on MMLU, GSM8K, and MetaTool benchmarks.

Key takeaway

For AI Security Engineers developing LLM agents, you must actively address over-privileged tool selection. Your current safety alignment methods may not prevent agents from choosing high-privilege tools unnecessarily, especially after transient failures. Consider implementing privilege-aware post-training, as demonstrated to reduce over-privileged use significantly (e.g., to 18.93% for Qwen3-4B-Thinking-2507) without degrading general performance. Prioritize robust error handling that encourages retries of lower-privilege options before escalating.

Key insights

LLM agents often select over-privileged tools, a risk mitigated by privilege-aware post-training.

Principles

Method

A privilege-aware post-training defense uses supervised fine-tuning (SFT) followed by reinforcement learning (RL) with a reward function penalizing premature high-privilege tool use and encouraging low-privilege exploration.

In practice

Topics

Code references

Best for: Research Scientist, CTO, VP of Engineering/Data, AI Scientist, AI Security Engineer, Machine Learning Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.SE updates on arXiv.org.