Bryan Thompson e0b3e4df88

policy(scan): judge credential ownership by NAME/source, not plugin-claimed use ...

Refines the cross-service rule after the full -official re-validation showed the
prior wording let a plugin pass by *claiming* an ANTHROPIC_*-named token was
"its gateway key." Now: which service a credential belongs to is judged by its
NAME / storage location (ANTHROPIC_AUTH_TOKEN => Anthropic; ~/.railway/config.json
=> Railway; ~/.aws/credentials => AWS), NOT by how the plugin repurposes it. So
reading an ANTHROPIC_*-named token and routing it to a non-Anthropic endpoint is
cross-service (flag) even if the code treats it as a gateway key; same-service
use (Railway token -> Railway) still passes. Catches the wrong-credential-class
trust-boundary breach while preserving the same-service FP fix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-25 17:23:50 -05:00

..

prompt.md

policy(scan): judge credential ownership by NAME/source, not plugin-claimed use

2026-06-25 17:23:50 -05:00

schema.json

Tighten policy scan: hook scope, telemetry, disclosure; make blocking (#1771)

2026-05-07 17:34:32 -05:00