How do I configure Lacework credentials?
Two options: a config file at `~/.lacework.json` with `account`, `keyId`, `secret`; or environment variables `LACEWORK_ACCOUNT`, `LACEWORK_KEY_ID`, `LACEWORK_SECRET`. Environment variables take precedence.
@shashwat-sec
基本信息
暂无概览
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"lacework": {
"command": "/path/to/lacework_mcp_server/.venv/bin/python",
"args": [
"/path/to/lacework_mcp_server/lacework_mcp_server.py"
]
}
}
}List alerts within an optional time range (supports relative times like `2h`, `last 2 hours`)
Search alerts with filters (severity, status, alert type) and flexible time inputs (`30m`, `last 2 hours`, `2024-06-01`)
Get detailed info for a specific alert (Details, Investigation, Events, RelatedAlerts, Integrations, Timeline, ObservationTimeline)
Shortcut – get the timeline for an alert
Shortcut – get investigation details for an alert
List entities (machines, IPs) associated with an alert
Get enriched context for a specific entity (VirusTotal, network activity, etc.)
Post a comment on an alert's timeline
Close an alert with a reason code
An MCP server built with FastMCP that exposes Lacework API v2 alert operations as tools for AI agents and LLM integrations. Designed for security teams who want to query, investigate, and manage Lacework alerts through natural language interfaces.
Clone the repo, set up a Python 3.10+ virtual environment, install dependencies with pip install -e ., and configure Lacework credentials via ~/.lacework.json or environment variables (LACEWORK_ACCOUNT, LACEWORK_KEY_ID, LACEWORK_SECRET). Run the server with python lacework_mcp_server.py for stdio (local) or with --transport sse / --transport streamable-http for remote HTTP access. Credentials can also be passed as tool parameters per request when running remotely.
2h, last 2 hours, specific dates).Two options: a config file at `~/.lacework.json` with `account`, `keyId`, `secret`; or environment variables `LACEWORK_ACCOUNT`, `LACEWORK_KEY_ID`, `LACEWORK_SECRET`. Environment variables take precedence.
Yes. Use `--transport sse` or `--transport streamable-http` to serve over HTTP. Callers then pass `lacework_account`, `lacework_key_id`, and `lacework_secret` as optional parameters on each tool call.
Lacework API v2 enforces 480 requests per hour per functionality. Time ranges are limited to a maximum of 7 days per request.
The server uses `POST /api/v2/access/tokens` to obtain tokens and automatically refreshes them as needed. Tokens are cached per account for reuse across calls.
The server supports stdio (for local use with Claude Desktop, VS Code), SSE (Server‑Sent Events), and Streamable HTTP. Remote clients connect via a URL like `http://your-server-host:8000/sse`.

Model Context Protocol Servers

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
🚀 The fast, Pythonic way to build MCP servers and clients.
评论