Case · DiggingBeagle record

OpenClaw Code Mode reportedly executed tools despite a PreToolUse denial

An open issue describes a permission hook returning deny while nested Code Mode shell and MCP operations still produced side effects.

Scope

One reporter supplied issue traces; upstream resolution, external reproduction and production abuse are not established.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade D
AI role
AGAINST AI
Basis and provenance

The pinned Claim and its primary disclosure support the described controlled result, but do not establish a population-wide rate or calibrated impact. The only available supporting evidence is the reporter's or advisory author's own account; independent reproduction has not been shown. Impact remains unbanded because no calibrated impact rubric for this particular evidence is established.

Assessed Nov 2, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Ask to execute a Code Mode tool

    The model produces a native nested tool request for shell or MCP.

    Boundary: Model output into executor command

  2. 02

    Hook denies the operation

    A PreToolUse callback communicates a deny result to the caller.

    Boundary: Policy decision into tool-call transport

  3. 03

    Execution still occurs in reported traces

    The nested executor allegedly performs the denied action instead of treating deny as a hard stop.

    Boundary: Advisory hook result into real host capability

Claims & evidence

CLM-2026-NOV02-OPENCLAW-CODEMODE-DENY-AThe reporter says OpenClaw 2026.7.1-2 with a Code Mode only Codex model executed three tool calls despite a before_tool_call denial response in the tested environment.supported

Basis: reported finding

Link to claim
CLM-2026-NOV02-OPENCLAW-CODEMODE-DENY-BAn OpenClaw reporter states that three nested Codex Code Mode calls executed in a sandbox after the pre-call policy hook returned and relayed deny decisions.supported

Basis: reported finding

Link to claim

Implications

An authorization callback must prevent the tool effect, not merely signal a refusal inside model-visible content.

Controls and mitigations

  • Enforce denial in the executor before dispatch; test actual OS and MCP side effects under nested tool calls with harmless markers.
  • Assert and test a negative postcondition at the actual shell or MCP server after every denied nested call, including code_mode_only execution.

Unknowns and contradictions

  • One reporter supplied issue traces; upstream resolution, external reproduction and production abuse are not established.
  • No independently replayed trace, fixed upstream version or comparison across all Codex tool modes is available.

Sources and citation

Material revision history

  1. Nov 2, 2026 · Canonical change recorded · new in release · revision 214