Sign inGet started
Paper · arXiv

Will the Agent Recuse, and Will It Stop? Measuring LLM-Agent Compliance with In-Band Governance Signals at the Access Door and Mid-Flight

As autonomous LLM agents hold real credentials and operate infrastructure without a human in the loop, operators cannot tell an agent a resource is off-limits, or ask a running agent to stand down. We propose an in-band governance signal -- the Recuse Signal -- that a server emits over a protocol's existing channels (an SSH banner, a PostgreSQL NOTICE, a Kubernetes admission warning) asking a connecting or running agent to voluntarily withdraw. It is a cooperative control (the robots.txt analogue for live access), not a security boundary; its value is empirical: do compliant LLM agents honor it? We define an open mini-standard (access-time deny/throttle/warn and mid-task halt), implement ...

AuthorsThamilvendhan Munirathinam
Primary categorycs.CR
Published4 June 2026
Last updated at source1 August 2026
cs.CRcs.AI
Embed this entry
<iframe src="https://silytics.si/embed/item/7f5c1e05-5532-45ff-8f59-559a2351f7ae" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.