bitwisecook/tcl-lsp/irule-review

iRule Security Review

Steps

1. Read ../_prompts/irules_system.md, then the iRule.
2. Call mcp__tcl-lsp__review with the contents as source. On a tool

error report it and suggest fixes.

1. Present the static findings (security, taint, thread safety; codes in

docs/generated/diagnostic_codes.md).

1. Go beyond them: unvalidated HTTP::uri / HTTP::query / HTTP::header /

HTTP::cookie input; information leakage in logs or HTTP::respond bodies; races on static:: or table state; DoS vectors (unbounded loops, expensive work in hot events); header injection via user data in HTTP::header insert/replace; open redirects via HTTP::redirect; session handling.

1. For each finding: description, affected lines, risk, recommended fix.

Output

### Static Analysis Findings from the tool, then ### Deep Analysis grouped by severity (critical, high, medium, low).

$ARGUMENTS