rxnorm-normalize

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (medium risk: 0.30). The runtime workflow for rxnorm.normalize takes the user-provided drug name string from the request and sends it to https://fittings.sh/v1/rxnorm/normalize (via call.mjs building a GET query), so outsider-authored free text is ingested and used by the service call.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill explicitly integrates a crypto payment flow: the service returns a 402 signed quote which the client must sign with a private key (example shows export FITTINGS_PRIVATE_KEY), the client can hold USDC on Base and will authorize settlement via a facilitator, and helper libraries (@x402/evm, signing/resigning) are referenced. The doc even instructs storing a wallet key and warns about it being in plaintext. This is a specific crypto/payment capability (signing authorizations and spending USDC), not a generic API caller or browser automation, so it grants direct financial execution authority.