ClawHub
Back to skill

Security audit

QwryAI

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed read-only connector for QwryAI, with the main risk being normal handling of a sensitive API key and workspace data access.

Install only if you trust QwryAI and the chosen agent with read-only access to the selected workspace. Store QWRYAI_API_KEY in an environment variable or secret manager when possible, avoid committing MCP configuration files that contain resolved tokens, and keep endpoints pointed at the official QwryAI HTTPS host unless you deliberately manage an alternative.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

External Transmission

Medium
Category
Data Exfiltration
Content
```json
{
  "url": "https://api.qwryai.com/mcp",
  "headers": {
    "Authorization": "Bearer ${QWRYAI_API_KEY}"
  }
Confidence
72% confidence
Finding
The sample configuration places a bearer token directly into an HTTP Authorization header for a remote MCP server, and later text says users may paste the API key directly into local config if interpolation is unavailable. While this is operationally common, it creates secret-exposure risk through local config leakage, backups, process inspection, screenshots, or accidental source-control commits.

External Transmission

Medium
Category
Data Exfiltration
Content
{
  "mcpServers": {
    "qwryai": {
      "url": "https://api.qwryai.com/mcp",
      "headers": {
        "Authorization": "Bearer ${QWRYAI_API_KEY}"
      }
Confidence
72% confidence
Finding
As with the earlier MCP example, this Cursor-style configuration embeds a bearer credential into a reusable client config pattern. If users resolve ${QWRYAI_API_KEY} manually or store secrets in plaintext config, the key may be exposed and grant read access to tenant-isolated workspace data such as conversations, knowledge, and analytics.

Static analysis

No suspicious patterns detected.