ClawHub
Back to skill

Security audit

Google SERP Maps Reviews API

Security checks for vulnerabilities and agentic risk

Overview

This skill is a focused API wrapper for fetching Google Maps reviews through Just Serp API, with disclosed network and API-key use.

Install this only if you intend to use Just Serp API and are comfortable providing JUST_SERP_API_KEY. Treat returned reviews and reviewer metadata as third-party API data, and avoid logging or sharing the API key.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill instructs the agent to invoke a network-capable helper (node .../run.mjs) against an external API but does not declare any explicit tool scope such as permissions or allowed-tools. This creates an authorization gap where review and runtime systems may not clearly constrain or surface the skill's outbound network behavior, increasing the risk of unintended external requests or misuse of the provided API key.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The documentation states that callers can set a two-letter language code for results, but it does not indicate that language selection should follow user preference or explicit opt-in. Because locale and language policy issues apply across all file types, this can be read as encouraging arbitrary language forcing without a documented user-choice safeguard.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.