Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Serper.dev search helper with expected third-party API calls, but users should avoid sending sensitive queries and should treat lead-generation contact data carefully.
Install only if you want an agent to query Serper.dev on your behalf. Do not use it with secrets, confidential business plans, regulated personal data, or private internal prompts. For lead generation, confirm that collecting and using business contact information complies with applicable laws, platform terms, and your organization's policies.
The invocation description is extremely broad ('any information', research, leads, businesses), making it likely to trigger for many generic user requests where sending the query to an external search provider may be unnecessary or unexpected. In agent settings, overbroad routing can cause inadvertent disclosure of sensitive prompts or user data to a third party.
The description does not warn that user queries are sent to Serper.dev, a third-party API, along with the API key in the request headers. Users or calling agents may therefore submit sensitive or proprietary search terms without understanding the external disclosure.
The repeated finding refers to the same outward network request to the Serper search endpoint. Although expected behavior for a search skill, it remains security-relevant because broad invocation language increases the chance that sensitive prompts are unnecessarily transmitted off-platform.
"Content-Type": "application/json"
}
payload = {"q": query, "num": num, "gl": gl}
r = requests.post("https://google.serper.dev/search", headers=headers, json=payload)
r.raise_for_status()
results = r.json().get("organic", [])
The repeated finding refers to the same outward network request to the Serper search endpoint. Although expected behavior for a search skill, it remains security-relevant because broad invocation language increases the chance that sensitive prompts are unnecessarily transmitted off-platform.
"Content-Type": "application/json"
}
payload = {"q": query, "num": num, "gl": gl}
r = requests.post("https://google.serper.dev/search", headers=headers, json=payload)
r.raise_for_status()
results = r.json().get("organic", [])
The skill metadata and top-level description frame the capability as generic web search returning organic results, but the file also exposes a Places workflow that returns addresses and phone numbers for lead generation. That mismatch can cause downstream systems or users to invoke the skill without realizing it collects and transmits business-contact queries to a third-party service, increasing privacy, compliance, and scope-of-use risk.
The repeated finding refers to the same Places endpoint request, which transmits user queries externally and enables structured collection of business contact information. The skill context makes this moderately more dangerous because it explicitly markets lead-generation usage, encouraging higher-volume harvesting of contact data.
"""
headers = {"X-API-KEY": os.environ["SERPER_API_KEY"], "Content-Type": "application/json"}
payload = {"q": query, "gl": gl}
r = requests.post("https://google.serper.dev/places", headers=headers, json=payload)
return r.json().get("places", [])
# Places returns website URLs + phone numbers directly — great for lead gen!
The repeated finding refers to the same Places endpoint request, which transmits user queries externally and enables structured collection of business contact information. The skill context makes this moderately more dangerous because it explicitly markets lead-generation usage, encouraging higher-volume harvesting of contact data.
"""
headers = {"X-API-KEY": os.environ["SERPER_API_KEY"], "Content-Type": "application/json"}
payload = {"q": query, "gl": gl}
r = requests.post("https://google.serper.dev/places", headers=headers, json=payload)
return r.json().get("places", [])
# Places returns website URLs + phone numbers directly — great for lead gen!
The lead-generation and Places guidance encourages collection of business websites, phone numbers, and addresses but omits compliance and acceptable-use warnings. While business contact data is often public, packaging it for lead generation through an external service can create privacy, terms-of-service, or policy issues if users are not informed.
No suspicious patterns detected.