Realm enforces explicit resource scope around tool-using agents rather than relying only on a language-model refusal. In the reported AgentDyn setup, an unconstrained agent experienced ninety-three successful attacks across 560 injection tests; the scoped design yielded one. The corresponding legitimate-task completion, however, dropped from forty-seven of…
Inspect the ClaimsCase · DiggingBeagle record
Realm resource scoping cut injection while also blocking many legitimate tasks
Realm reported a large attack-success reduction in one benchmark but nearly halved authorized task completions under its resource restrictions.
Controlled AgentDyn evaluation with Qwen3.5 Flash and selected injections; observed reductions and task failures do not translate directly to heterogeneous production deployments.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- mitigation available
- AI role
- AGAINST AI
Basis and provenance
The study provides a matched benchmark with a utility tradeoff; no production reduction in incidents is claimed. Impact remains unrated because the scoped record does not establish a calibrated severity-to-impact-band mapping.
Assessed Oct 31, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-C26-REALM-SCOPE-UTILITY-1 · Realm: scoped resources for tool-using agent injection defense
At a glance
The attack-rate improvement is meaningful within the benchmark but accompanied by material loss of legitimate capability.
Read the implicationsGeneralization to environments with complete asset discovery is not measured. The remaining allowed-tool attack requires separate action-intent controls.
Limits and uncertaintyFull account
Realm enforces explicit resource scope around tool-using agents rather than relying only on a language-model refusal. In the reported AgentDyn setup, an unconstrained agent experienced ninety-three successful attacks across 560 injection tests; the scoped design yielded one. The corresponding legitimate-task completion, however, dropped from forty-seven of sixty to twenty-four of sixty. Both denominators belong in the finding. A safeguard that sharply lowers attacks while also denying ordinary authorized work is not a complete production solution.
The paper reports at least one attack still operating through an allowed calendar tool, demonstrating that resource scoping cannot detect every malicious purpose inside an otherwise permitted capability. Real implementations must identify legitimate assets and design task-specific approvals so that the model is not simply deprived of most useful tools. This study is an authorization tradeoff experiment, not evidence of live incidents eliminated.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Timeline
- Oct 30, 2026disclosure
Public disclosure
Claims & evidence
CLM-C26-REALM-SCOPE-UTILITY-1Realm reports 93 of 560 successful injections and 47 of 60 completed legitimate tasks in a baseline, versus one of 560 injections and 24 of 60 legitimate tasks under resource scoping.supported
Basis: reported finding
- supportsRealm: scoped resources for tool-using agent injection defenseprimary disclosure
Realm paper, AgentDyn attack and legitimate-task result tables
Implications
The attack-rate improvement is meaningful within the benchmark but accompanied by material loss of legitimate capability.
Controls and mitigations
- Scope actual asset and task permissions rather than merely removing tools; measure task completion and hostile outcomes with equal importance.
Unknowns and contradictions
- Generalization to environments with complete asset discovery is not measured.
- The remaining allowed-tool attack requires separate action-intent controls.
Sources and citation
Material revision history
- Oct 31, 2026 · Canonical change recorded · new in release · revision 208