Support authoritative `allow`, `deny`, and `ask` verdicts from hooks

Feature request for product/service

Cursor IDE

Describe the request

Feature request: make hook verdicts authoritative so preToolUse can force allow, deny, or ask, with priority over permissions.json and stored IDE allowlists.

Today preToolUse hooks can return allow, deny, and ask, but only deny meaningfully changes what runs. allow and ask do not override permissions.json or persisted IDE allowlist state such as state.vscdb.

This would let project hooks define real policy. Require approval for sensitive commands, block risky ones, and bypass auto-run when appropriate without fighting the existing prefix-only permission stack.

Operating System (if it applies)

Linux

Hey @ragnoroct!

Thanks for the feedback. We have an open bug ticket for fixing this for preToolUse, as right now only deny is respected. I added your report and bumped up the priority (we’ve had a couple reports).