Back to skill

Security audit

Amazon Product Details API

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to be a focused JustOneAPI Amazon product lookup wrapper, but it handles the API token in ways that can expose the credential through command arguments and request URLs.

Review before installing if the JustOneAPI token has billing or broad account privileges. Use a least-privilege token, avoid logging commands or full request URLs, rotate the token if it may have appeared in logs, and prefer a version that reads the token from the environment and uses header-based authentication if the service supports it.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
bin/run.mjs:20
Finding

API Token Exposed Through Process Arguments and URL Query Parameters

Content
View full analysis
parameter.name === "token"); if (!tokenParam || params.token !== undefined) { return; } if (!cliToken) { fail("--token is required for this operation.", { operationId: operation.operationId, }); } params.token = cliToken; } ``` All query parameters, including the token, are appended to the request URL: ```js function applyQueryParams(operation, params, url) { for (const parameter of operation.parameters.filter((item) => item.location === "query")) { const value = params[parameter.name]; if (value === undefined) { continue; } app ...[truncated 3106 chars]
Remediation
View remediation
`, if the JustOneAPI service supports header-based authentication. 3. If the upstream service strictly requires query authentication: - Avoid logging the constructed URL. - Add centralized redaction that replaces the `token` query value before URLs can enter diagnostics or telemetry. - Ensure reverse proxies, gateways, access logs, application monitoring, and tracing systems redact or omit the `token` parameter. - Use narrowly scoped, short-lived, and regularly rotated tokens. 4. Reject `token` values supplied inside `--params-json` so callers cannot bypass the safer environment-based credential path. 5. Update `SKILL.md` to use an invocation without a token argument: ```bash JUST_ONE_API_TOKEN="$JUST_ONE_API_TOKEN" node {baseDir}/bin/run.mjs \ --operation "getAmazonProductDetailV1" \ --params-json '{"asin":""}' ``` 6. Document the residual logging risk if query-string authentication cannot be replaced, and provide immediate token-revocation and rotation guidance. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding

The skill invokes a network-capable helper (node .../bin/run.mjs) and requires an API token, but it does not declare an explicit tool scope such as permissions or allowed-tools. This creates a governance gap: a host may not clearly constrain or surface the skill's outbound network behavior, increasing the risk of unexpected external requests or misuse of user-supplied data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill sends the API authentication token as a query parameter, which places the secret directly in the URL. URLs are commonly logged by clients, proxies, gateways, browser/history tooling, and observability systems, so the token can be exposed outside the intended trust boundary even when HTTPS is used. In this skill context, the token is required for every request to a third-party API, making the exposure more meaningful because compromise of the token enables unauthorized API usage and possible quota or billing abuse.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill documentation instructs callers to provide an authentication token as a query parameter to an external API but does not warn that this transmits credentials off-platform. Query-string credentials are especially risky because they may be logged by clients, proxies, gateways, analytics systems, and browser history, increasing the chance of accidental token disclosure. In this skill context, the risk is more relevant because the skill is explicitly a wrapper around a third-party API, so users may unknowingly expose sensitive API secrets to an external service.

Content

No source excerpt is available for this finding.