The README explicitly requires `GOOGLE_PLACES_API_KEY`, which is a sensitive third-party API credential with potential billing impact if exposed. The material does not indicate collection of other highly sensitive credentials.

By design, the tool sends query content to the Google Places API. It also supports optional `GOOGLE_PLACES_BASE_URL` for testing/proxying, meaning traffic can be redirected to a custom proxy endpoint. This is normal egress within its stated purpose, with no evidence of unrelated hidden exfiltration.

The material only describes a place-query CLI/skill and does not show arbitrary user code execution, launching unrelated system processes, or requesting system privileges beyond its stated function.

There is no indication that it needs to read or write local files, databases, clipboard data, browser contents, or other sensitive local resources; its data scope appears limited to user-supplied query parameters and API responses.

The source is an open-source GitHub repository with extremely high community adoption (~377k stars), which materially lowers supply-chain risk. Although the license is unspecified and maintenance status is unknown, there are no high-risk signals such as closed-source distribution, apparent abandonment, or suspicious delivery channels.