phantom-snare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIGIL_API_KEY | No | API key for VIGIL ingestion. | |
| VIGIL_MIN_LEVEL | No | Minimum threat level to emit to VIGIL (default: INJECTED). | INJECTED |
| VIGIL_INGEST_URL | No | VIGIL HTTP ingest endpoint for structured threat events. | |
| VIGIL_QUEUE_PATH | No | File path for VIGIL file queue (VIGIL tails this file). | |
| PHANTOM_SNARE_COOLDOWN | No | Session cooldown in seconds between alerts (default: 60). | 60 |
| PHANTOM_SNARE_MIN_LEVEL | No | Minimum threat level to trigger alerts (default: INJECTED). | INJECTED |
| PHANTOM_SNARE_SLACK_URL | No | Slack webhook URL for alerting. | |
| PHANTOM_SNARE_DISCORD_URL | No | Discord webhook URL for alerting. | |
| PHANTOM_SNARE_WEBHOOK_URL | No | Generic HTTP endpoint for alerting. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileB | Read the contents of a file from the filesystem. |
| web_searchC | Search the web for information and return relevant results. |
| execute_codeA | Execute code in a sandboxed environment and return the output. |
| send_emailA | Send an email to a specified recipient. |
| database_queryC | Execute a SQL query against the application database. |
| get_user_infoB | Retrieve user account information and profile data. |
| list_directoryB | List the files and directories at a given path. |
| list_filesC | List files matching a path or pattern. |
| create_fileC | Create a new file with the given contents. |
| write_fileC | Write or overwrite the contents of a file. |
| delete_fileA | Delete a file from the filesystem. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Several tools overlap in purpose: list_directory and list_files both explore the filesystem, and create_file and write_file both handle file creation/overwriting. The remaining tools are distinct enough, but the boundaries between these filesystem tools are ambiguous.
Most tools follow a consistent snake_case verb_noun pattern like read_file, delete_file, create_file, and get_user_info. Minor deviations exist: web_search is object-verb rather than verb-object, and database_query reads more like a noun phrase than query_database.
Eleven tools is within a reasonable range and not bloated. However, the tools span unrelated domains—filesystem, web, code execution, email, database, and user info—so the count feels broad rather than tightly scoped.
The filesystem tools have decent CRUD coverage, but database_query only supports queries, get_user_info only retrieves data, and there are no update/rename/copy operations for files. The surface is shallow in each mini-domain, and the duplicate create_file/write_file pair suggests an incomplete or muddled design.