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`.
MCP Toolbox for Databases is an open source MCP server for databases.
A curated list of references for MLOps

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.

Health by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one

Model Context Protocol Servers
コメント