Allowing only read and search removes approval friction for operations that inspect repository content without modifying it. The edit and execute tools remain available in the agent profile, but they continue to require explicit approval because they are not included in the command's approval bypass.
Using no option preserves the default approval behavior for all tools, including low-risk inspection tools, which does not meet the velocity requirement. Allowing all tools would remove the approval safeguard for file modifications and shell execution. Denying edit and execute prevents those tools from being used at all, rather than keeping them available under human control.
This design separates tool availability from automatic authorization. Read-only operations can proceed autonomously, while potentially impactful operations remain subject to a human decision at the point of use.
Study-guide topics: tool approval boundaries, least privilege, read-only execution, and controlled agent autonomy.