ClawHub
Back to skill

Security audit

Clarity Fold Status

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small status checker that makes disclosed read-only API requests to Clarity Protocol and optionally uses a single documented API key environment variable.

Before installing, understand that running the skill contacts clarityprotocol.io and may send CLARITY_API_KEY if you set it. Do not set that environment variable unless you trust the Clarity Protocol service and want the higher rate limit.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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)

Lp3

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding
The skill advertises network access and optional use of an environment variable API key, but it does not declare an explicit tool scope such as permissions or allowed-tools. That creates an authorization ambiguity where an agent may invoke network or read environment-backed secrets without clear least-privilege constraints, increasing the risk of unintended external requests or secret exposure.

Vague Triggers

Medium
Confidence
93% confidence
Finding
The invocation description uses broad phrases like 'when the user asks about fold status, how many variants, research overview, what data is available, or Clarity Protocol status,' which can cause over-triggering outside a tightly defined scope. Overbroad activation is dangerous because it may cause unnecessary network access or API-key-backed requests in contexts where the user did not clearly intend to call this external skill.

Static analysis

No suspicious patterns detected.