An architect is reviewing an internal research assistant with eleven connected tools. Several were added during prototyping and are rarely called. What review step does least-privilege tool configuration call for?
Choose an answer to check it. Afterward, select any option to review its explanation.
Tempting because unused tools seem harmless, but a connected tool stays reachable whether or not the model usually calls it. Leaving it connected keeps the attack surface and cost the audit exists to remove.
Clearer names may help tool selection, but renaming removes nothing. The tools remain connected and callable, so the scope problem the review is meant to fix is untouched.
This uses convenience as the test, which is exactly the criterion the audit rejects. The question for each tool is whether the task requires it, not how easy it is for the team to keep.
Least-privilege configuration treats every connected tool as attack surface and cost. Each tool is tested against the task (essential or merely convenient), out-of-scope tools are removed, and the reason for each removal is recorded so the audit can be defended later.
id q5a85e55710