AGENTFORCE-AF-18: Clear-Text Agent Client Token in Mule Configuration
🔴 High · Credential Exposure
Detects bearer tokens and API keys stored in clear text in a Mule app's properties / YAML (or literally in an Authorization / x-api-key header) and sent by the app's A2A, MCP or agent HTTP clients. Encrypted values (![...]), ${secure::...} references, environment references and placeholders are skipped.
Details
| Field | Value |
|---|---|
| Rule ID | AGENTFORCE-AF-18 |
| Severity | High |
| Category | Credential Exposure |
| Compliance | SOC2_CC6, PCI_DSS |
Remediation
Rotate the credential first: it stays in git history even after you delete the line. Then remove the clear-text value and use Mule secure properties: put the encrypted value (![...]) in a secure-*.yaml or .properties file loaded by <secure-properties:config>, read it with ${secure::key}, and pass the encryption key at deploy time (runtime property or Anypoint Secrets Manager), never in the repository. Then add secret scanning (for example gitleaks) to CI so it does not come back.