Back to skill

Security audit

高德地图

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward AMap route-planning helper, with privacy and credential-handling caveats but no hidden or destructive behavior found.

Install only if you are comfortable sending route origins, destinations, and resulting coordinates to AMap. Configure a dedicated AMap Web Service API key in ~/.openclaw/credentials/amap.json, and avoid entering sensitive home, client, or confidential business locations unless that disclosure is acceptable.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Context-Inappropriate Capability

Medium
Confidence
94% confidence
Finding
The script bypasses the declared AMAP_API_KEY configuration mechanism and instead reads credentials from a fixed file path in the user's home directory. This creates hidden credential coupling, increases the chance of using unintended secrets, and can expose or misuse credentials in environments where that file is present unexpectedly.

Intent-Code Divergence

Medium
Confidence
91% confidence
Finding
The documentation states one credential mechanism while the code uses another, which is a security-relevant mismatch because operators may believe the script uses scoped runtime configuration when it actually reads a local secrets file. This can lead to accidental credential exposure, misconfiguration, and weaker auditing of how secrets are accessed.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill documentation encourages geocoding and route queries without warning that origin/destination data is sent to AMap's external service. Location queries can contain sensitive personal or business travel information, so users may unknowingly disclose private data to a third party.

Missing User Warnings

Medium
Confidence
83% confidence
Finding
The script transmits user-supplied origin and destination data to the external Amap geocoding service without an explicit notice at execution time. Because location inputs can be sensitive, this creates a privacy risk for users who may not realize their addresses or travel endpoints are being sent to a third party.

Static analysis

No suspicious patterns detected.