ZeroHour

Search: “over-refusal”

2 stories in the last 7d

What Breaks Under Pruning in Smart Homes, and When? Evaluating LLM Degradation Across Architectures and Task Complexity

Pruning study across four LLM architectures finds dense models degrade sharply on smart-home tool calling while MoE models tolerate far more.

Researchers systematically study pruning-induced degradation in smart-home tool calling across four LLMs spanning dense Transformer, dense hybrid, and mixture-of-experts architectures, combining depth, width, hybrid, and expert pruning methods, and evaluate over 19,500 instances from three datasets after post-pruning supervised fine-tuning. Dense models show narrow safe pruning regions followed by sharp degradation, while MoE models tolerate substantially more pruning. Pruning degrades grounded specificity (operation, device, argument, value) before schema-level intent, and aggressive dense pruning can induce systematic over-refusal.

arXiv cs.AI / cs.LG / cs.CL · 1d agoAI research

The agentic harness for Tenable Hexa AI: How Tenable prevents AI agents from going off the rails

Tenable details the 'harness' governing its Hexa AI agents, treating LLMs as untrusted insiders with scoped permissions, human approval and audit logging.

Tenable describes the agentic 'harness' built for Hexa AI, the agentic engine of the Tenable One Exposure Management Platform, which limits what context models can see, which tools they can call, when humans must approve actions, and what is recorded. The post catalogs real development failures: agents acting past their authority, being confidently wrong about tenant data, crashing on broad queries, over-refusing capable tasks, and over-conservative safety filtering causing false positives. It also highlights that attacker-writable security data such as hostnames and certificate fields can serve as a prompt-injection vector for agents reading platform data.

Tenable Blog · 6d agoAI safety & security