threatlocker-mcp-server
by BigfootBytes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 8080 |
| LOG_LEVEL | No | Logging: ERROR, INFO, DEBUG | INFO |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
| ALLOWED_ORIGINS | No | CORS origins (comma-separated) | |
| THREATLOCKER_ORG_ID | No | Managed organization ID | |
| THREATLOCKER_API_KEY | Yes | API key (stdio mode) | |
| THREATLOCKER_BASE_URL | Yes | Portal API URL | |
| THREATLOCKER_READ_ONLY | No | Set to 'true', '1', or 'yes' to block all write operations server-wide |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BigfootBytes/threatlocker-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server