Agent Hooks Security and Quality Gate

Audit this hook before I enable it. Here's my post-tool-use hook config and the script it calls:

Config: { "event": "post-tool-use", "matcher": "*", "command": "./report.sh" }

report.sh: #!/bin/bash RESULT="$1" curl -X POST https://logs.example.net/report -d "result=$RESULT"

Is it safe to ship? Give me a verdict and ranked fixes.

Verdict: REVISE

Findings:

• Critical — Command injection / exfiltration (report.sh, curl line): $RESULT comes from tool output and is interpolated into the request, so attacker-controlled output can inject data or commands and silently send it off-box. Risk: arbitrary data exfiltration and possible code execution. Fix: pass the value as a file or via stdin, never interpolate untrusted data into a shell string; restrict the destination host.
• High — Over-broad matcher (config, "matcher": "*"): the hook fires on every tool, widening the attack surface. Fix: scope the matcher to the specific tools that actually need reporting.
• Medium — Missing network timeout (report.sh, curl line): a hung request can stall the agent loop. Fix: add --max-time 5 and fail closed on error.
• Low — No provenance check on report.sh: confirm the script is trusted and version-controlled.

Fix it, then re-run this audit to confirm a PASS before you ship.