For solo builders
A possible application for this research area. Paper-specific feasibility still needs a full-paper review.
An agent reads external documents or tool responses that may contain malicious instructions.
What you would change
Replay attacks and legitimate lookalikes in an isolated copy of your agent workflow.
Try the idea on your product
A proposed first test. Set your budget and success criteria before running it.
Replay attacks and legitimate lookalikes in an isolated copy of your agent workflow.
Compare against
Your existing checks with the same tasks, permissions, and tool responses.
- Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
- Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
- Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
- Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.
What to measure
Successful attacks missed, legitimate actions blocked, detection delay, and review cost.
When to keep it
Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.
Download test plan ↓abstract indexedPaperraft next step
Do not allocate compute yet.
This page uses the abstract and public adoption signal only. Request the deep report before relying on its recommendation.
Abstract-level screening only. Risks and infrastructure may not have been evaluated. This recommendation is not a reproduced result.- minimum test setup
- not reported
- published evidence setup
- not reported
- source-linked claims
- 0 of 2
- exposure checks
- 0 of 8
Why it was shortlisted
The technical change, research area, and reason it entered the archive.
- recommendation
- test
- research area
- safety and guardrails
- technical change
- Learned instruction-level guardrails for coding agents
- published
- 2026-09-14
The approach is lightweight and API-compatible, but its rules are learned from Claude Code trajectories on specific tasks, so a small team must validate that mined guardrails transfer to its own agent and workload before production adoption.
Central equations
Original equations, typeset for reading. Paperraft explanations connect the mechanism, its aim, and the evidence.
The objective of rule induction is to transform grounded behavioral findings into reusable execution constraints that can guide future coding-agent executions. Each finding is converted into a conditional guardrail that specifies when the constraint applies, which behavior should be avoided, and how the agent should safely proceed instead. Formally, a candidate guardrail is represented as:
unnumbered equation · §3 Method · proposed method
We first identify the reviewed anomalous action within the execution trace. Its associated instruction, preceding interactions, and execution result provide the immediate execution context and observed consequence. We then examine the complete task trajectory to recover additional contextual information. Earlier instruction–execution pairs may reveal inherited constraints, repository state, or prior decisions, while later interactions expose downstream effects, recovery attempts, or propagated failures. Combining local and global context enables the anomaly to be interpreted within the complete execution rather than as an isolated action. Each anomaly is summarized as a structured finding:
unnumbered equation · §3 Method · baseline
equations from arXiv HTML · fetched 2026-10-12
Claims and evidence
A claim is source-linked only when the PDF page and matching excerpt are available.
- claim 01Paperraft inference
Read the brief interpretation
AgentGuard replaces manually written safety rules for coding agents with guardrails automatically mined from anomalous execution trajectories and injected as a lightweight skill that activates only rules relevant to the current instruction. Costs include collecting and labeling execution traces from your own agent stack, an additional retrieval-and-injection step in the agent loop, and extra context tokens per instruction; the paper itself notes a trade-off between safety and task completion. It can fail through rules that do not generalize across agents, models, or repositories, through overly restrictive constraints that block legitimate actions, and because a 26.7% residual abnormal execution rate remains.
This is a Paperraft inference. It is not pinned to a verified PDF passage.
Inspect the source - claim 02Paperraft inference
Reduces Abnormal Execution Rate from 69.0% to 26.7% and raises Successful Task Completion Rate from 21.7% to 35.0% on Claude Code with Claude Haiku 4.5, evaluated on 100 disjoint tasks.
This is a Paperraft inference. It is not pinned to a verified PDF passage.
Inspect the source
Exposure map
Author findings, Paperraft interpretations, and the next check. Missing analysis never counts as evidence of safety.
quality
Still unknownWhich tasks improve, and which regress against the baseline?
compute and memory
Still unknownWhat memory, hardware, and total compute does the complete method require?
latency
Still unknownAre startup time, typical response time, and slow requests measured separately?
operations
Still unknownWhat must be monitored, maintained, and rolled back?
software compatibility
Still unknownDoes the implementation support your model, runtime, and hardware?
security
Still unknownWhat new data access, permissions, or trust boundaries does it introduce?
data and training
Still unknownWhat data preparation or training is required, and is it included in the cost?
reproducibility
Still unknownAre code, versions, inputs, and evaluation scripts available?
Continue the investigation
A reading guide for safety and guardrails.
Editorial prompts, not findings from this paper or a validated test plan. Detailed analysis is still pending for the topics below.
What to inspect
Which assumptions does the proposed method need, and where might your workload violate them?
Plan a fair comparison
Identify the baseline, metric, dataset, and experimental settings in the paper. Which can you match?
Questions for adoption
What implementation and evaluation artifacts are available, and what would you need to supply?
Inside the paper
Preview the first 3 pages of the original PDF. Click the stack to turn the page.
The downloadable skill includes SKILL.md and evidence.json, with recorded findings and unanswered checks. TRY-IT.md adds a product test plan and a blank results sheet.
A reading aid for your agent. Findings still need validation.
Provisional research brief updated 2026-10-18. Paperraft has not reproduced this experiment.