Unverified50% confidenceDecision RuleExact time
In the Harness, all tool executions must go through the full pre-tool use check, including commands with run_in_background=true, and background execution cannot bypass the check.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/15/2026
First Seen
Valid until: 1/13/2027
Sources
Related Entities
Related Claims
UnverifiedThe System prompt instructs the model that only independent commands should be placed in the background for execution, and only commands whose subsequent work does not wait for their results are suitable for enabling run_in_background.67% similarUnverifiedThe allowedTools configuration is only responsible for skipping permission confirmation prompts and is not responsible for whether a tool can be invoked.65% similarUnverifiedAn agent that is completely idle (calling no tools and outputting no text at all) can pass all safety test cases that only check 'does not call tools' without checking reply content.62% similarUnverifiedA Dry Run must be conducted before formal execution; the Dry Run only checks the plan and does not call the real business interface.60% similarUnverifiedWhen a coding agent's hook crashes, times out, or points to a nonexistent script, most tools by default choose to let it pass (fail-open).58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1033467API
curl https://kongchang.com/api/v1/knowledge/claims/1033467MCP
get_claim(id=1033467)