First Seen
Feb 19, 2026
Last Scanned
Feb 22, 2026
Findings
4
Score
67/100
Findings (4)
Text combines credential access with network transmission
First, generate a dedicated webhook secret for this integration — do NOT reuse your gateway's global hooks.token or any other existing credential:Remove the combination of credential access and network transmission from the tool. If the tool needs credentials, access them via a secrets manager and never transmit them externally.
Likely FP if the tool legitimately uses credentials for API authentication (e.g., reading an API key to make authenticated requests to the same service).
Detects fetching remote documentation or code to load as agent context
fetch it, read + https://autonoma.city/heartbeat.mdPin the SDK or script to a specific version and verify its checksum after download. Prefer installing SDKs via a package manager instead of fetching remote scripts directly.
Likely FP if the match is documentation showing how to install an official SDK (e.g., Google Cloud SDK, AWS CLI) from its canonical URL.
Detects URLs fetched at runtime that control or influence agent behavior without pinning
Fetch https:// + promptAvoid loading configuration or behavior-controlling content from runtime URLs. Bundle required configurations locally or pin remote config to versioned, integrity-verified endpoints.
Likely FP if the URL in the match is a documentation link or example URL (e.g., example.com) rather than an actual runtime-fetched configuration endpoint.
Detects patterns where external API responses are used directly without validation or sanitization
API calls in one session. The response + automatically lifted. Due processValidate and sanitize all data received from external APIs before using it in tool operations or agent prompts. Implement schema validation and treat API responses as untrusted input.
Likely FP if the match is a truncated table cell or documentation fragment that mentions API responses in a descriptive context, not actual unvalidated data processing.