Skills/PyPI/semlayer

semlayer@0.7.0b8

CAUTION· not started

Publisher claims: "Semantic layer inference engine for data warehouses, with an openly licensed format" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server) · listed in the official MCP RegistryPublisher semlayer-dev · publishing for 125 daysInstalls 971Last detonated 1 h ago

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
ANTHROPIC_API_KEYPG_DSNSNOWFLAKE_AUTHENTICATORSNOWFLAKE_PRIVATE_KEY_PASSPHRASESNOWFLAKE_PRIVATE_KEY_PATHConfiguration, not credentials: CODEX_HOME, COPILOT_HOME, GCP_PROJECT, MESSY_SCALE, PG_ROLE, PGDATABASE, SEMLAYER_HOME, SEMLAYER_TELEMETRY, SNOWFLAKE_ACCOUNT, SNOWFLAKE_DATABASE, SNOWFLAKE_HOME, SNOWFLAKE_ROLE, SNOWFLAKE_WAREHOUSE
Where it talks to
semlayer.dev (its own)
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for ANTHROPIC_API_KEY, PG_DSN, SNOWFLAKE_AUTHENTICATOR, SNOWFLAKE_PRIVATE_KEY_PASSPHRASE, SNOWFLAKE_PRIVATE_KEY_PATH and talks to semlayer.dev. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets ANTHROPIC_API_KEY=semlayer.dev,PG_DSN=semlayer.dev,SNOWFLAKE_AUTHENTICATOR=semlayer.dev,SNOWFLAKE_PRIVATE_KEY_PASSPHRASE=semlayer.dev,SNOWFLAKE_PRIVATE_KEY_PATH=semlayer.dev -- uvx semlayer

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/semlayer/mcp_server.py:546 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvariables, `$SEMLAYER_HOME/.env`, dbt's profiles.yml and Snowflake'sFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/connectors/bigquery.py:149 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Connect using .env credentials; persona 'reader' (product) or 'admin'.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/llm/provider.py:186 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesflag, else `SEMLAYER_MODEL` in the `.env` file, else the cheap tier.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/llm/provider.py:46 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`--model` and the MCP server picks up from the same `.env` file the API keyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/env_file.py:118 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""The `.env` file this module is about: `$SEMLAYER_HOME/.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/session.py:89 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""The `.env` file the agent prescribes lines in. Re-read on every call.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/env_file.py:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprescribe -- is a file: `$SEMLAYER_HOME/.env`, default `~/.semlayer/.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/env_file.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesA `.env` here is the user's own file in their own home directory, so it isFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/cli.py:68 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesf"{CHEAP_MODEL}; SEMLAYER_MODEL in $SEMLAYER_HOME/.env is the "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Credential pass-through configurationsrc/semlayer/cli.py:104 · Credential pass-through configuration — agent relays sensitive credentials"(repeatable). Doc text IS sent to the LLM — don't pass secrets. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
HIGH
Access to sensitive file pathssrc/semlayer/env_file.py:2 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""The `.env` file semlayer reads, and the only way its values reach a run.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/mcp_server.py:478 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"their environment, their `.env` file, their dbt profile, or their "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/session.py:260 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# names for the same thing, and the `.env` line to prescribe when a credentialFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Process kill commandsrc/semlayer/link/run.py:11 · Process kill command — agent can terminate processes- LLM-implausible kills the candidate; the kill is recorded (provenance ofFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/session.py:1614 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""The model key, from the `.env` file or the environment.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/session.py:1453 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesThe `.env` file is applied for the duration of the open and takenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Process kill commandsrc/semlayer/drift.py:101 · Process kill command — agent can terminate processesits old name used to kill the whole drift run.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification commandsrc/semlayer/init_cmd.py:36 · File permission modification command — agent changes file ownership/permissions-- mkdir -p ~/.snowflake/keys && chmod 700 ~/.snowflake/keysFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
LOW
Dynamic module loadingsrc/semlayer/session.py:326 · Dynamic module loadingreturn importlib.util.find_spec(module) is not NoneFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedsrc/semlayer/cli.py:622 · Python subprocess execution detectedr = subprocess.run(["git", "config", "user.name"], cwd=Path(doc_path).resolve().parent,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Access to sensitive file pathssrc/semlayer/session.py:99 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""The process environment with `$SEMLAYER_HOME/.env` layered on top.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedsrc/semlayer/session.py:659 · Python subprocess execution detectedr = subprocess.run(["git", "config", "user.name"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Process kill commandsrc/semlayer/link/run.py:212 · Process kill command — agent can terminate processessurvives to the accept/review/kill decision (best_for_child).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈56 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for semlayer@0.7.0b8 as of 38 min ago. This is the package itself, not its dependencies.

What would make this Verified

4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim semlayer-dev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  5. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
  6. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim semlayer-devPropose a patch to the maintainer