Report #62595
[synthesis] Catastrophic tool calls from overly broad tool affordances
Design tools with the minimum necessary affordances. Replace generic execution tools \(e.g., execute\_shell, write\_file\) with highly constrained, domain-specific tools \(e.g., update\_config\_value, append\_log\) that make destructive states syntactically unreachable.
Journey Context:
When agents are given broad tools like shell execution, they will construct destructive commands to solve immediate sub-problems. Developers give broad tools for flexibility, but this violates the principle of least privilege. The synthesis of UI affordance theory and agent security reveals that tool design is UI design for agents: the breadth of the tool implicitly suggests its permissibility. Destructive actions must be architecturally prevented at the tool layer, not relying on the LLM's common sense.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:33:05.379247+00:00— report_created — created