NEXUS: Structured Runtime Safety for Tool-Using LLM Agents
Researchers have introduced NEXUS, a structured runtime safety monitor for tool-using LLM agents, which applies a formal intervention policy to ensure safe execution of high-impact actions. NEXUS combines deterministic safety rules, argument-level inspection, and a calibrated logistic-regression risk score for graded escalation. The system has achieved high accuracy and low latency in various benchmarks, making it a promising solution for runtime safety monitoring.
- ▪NEXUS is a structured-plan safety monitor that applies a formal intervention policy to select among four actions: allow, block, request confirmation, or request revision.
- ▪The system combines deterministic safety rules, argument-level inspection, and a calibrated logistic-regression risk score for graded escalation.
- ▪NEXUS has achieved an F1 score of 0.949 and a 4-class intervention accuracy of 0.6406 on a 128-instance synthetic benchmark.
arXiv cs.AI files mainly under ai research. We currently carry 1,128 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | arXiv.org |
| Canonical URL | https://arxiv.org/abs/2607.19356 |
| Publication time | Thu, 23 Jul 2026 00:00:00 -0400 |
| Retrieval time | 2026-07-23T04:57:25.949Z |
| Last seen | 2026-07-23T08:18:16.370Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | HmcbDtlVgO7w |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Computer Science > Artificial Intelligence arXiv:2607.19356 (cs) [Submitted on 25 May 2026] Title:NEXUS: Structured Runtime Safety for Tool-Using LLM Agents Authors:Elias Hossain, Md Mehedi Hasan Nipu, Tasfia Nuzhat Ornee, Rajib Rana, Niloofar Yousefi View a PDF of the paper titled NEXUS: Structured Runtime Safety for Tool-Using LLM Agents, by Elias Hossain and 4 other authors View PDF HTML (experimental) Abstract:Tool-using LLM agents increasingly execute high-impact actions, making runtime safety monitoring essential. We present NEXUS (Neural EXecution Utility and Safety), a structured-plan safety monitor that applies a formal intervention policy to select among four actions: allow, block, request confirmation, or request revision.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at arXiv.org.
Discussion
0 commentsMore from arXiv.org
