How to Use the Lacework (Cloud Security & CNAPP) MCP in Cursor

Q: How do I use Lacework (Cloud Security & CNAPP) to audit running hosts inside Cursor?

Run listhostvulnerabilities within Cursor to fetch active CVEs on your EC2 or GCE virtual machines. Cursor uses this live data to suggest specific package upgrades or configuration changes directly in your active code files.

Q: Can Cursor search my cloud inventory using the Lacework (Cloud Security & CNAPP) MCP Server?

Yes, Cursor calls searchcloudinventory to pull a real-time list of active cloud assets, networking perimeters, and S3 buckets. This lets the AI editor analyze your live infrastructure topology as you write deployment scripts.

Q: How does Lacework (Cloud Security & CNAPP) help me isolate staging and production resource groups in Cursor?

Your Cursor agent uses this MCP Server to execute listresourcegroups to distinguish between staging and production environments defined in your policies. This ensures your automated code fixes target the correct scope without accidentally modifying critical production resources.

Q: Where do I add the configuration block to run these security tools in my Cursor workspace?

You create a .cursor/mcp.json file in your project root and add the server definition under the mcpServers key. Once saved, Cursor's agent mode instantly gains access to all ten cloud security tools.

Q: Does Vinkius keep my cloud telemetry, container SHAs, and network perimeters private?

Absolutely, all telemetry fetched via getalert is processed inside an ephemeral, zero-trust sandbox. Vinkius never logs your raw cloud security alerts or vulnerability payloads, keeping your proprietary infrastructure data completely private.

Fix vulnerabilities and query active threat alerts while writing code with Lacework inside Cursor agent mode.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lacework (Cloud Security & CNAPP) MCP to Cursor

Create your Vinkius account to connect Lacework (Cloud Security & CNAPP) to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Lacework (Cloud Security & CNAPP) with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Patch CVE exposures directly in Cursor

`search_cve_exposure` allows Cursor to search your entire infrastructure footprint for specific vulnerabilities like Log4j while you edit files in agent mode. Your agent identifies the affected host machines and helps you modify the relevant configuration files or infrastructure-as-code manifests in real-time. By running this MCP Server, Cursor checks if active processes are executing vulnerable code on your VMs, letting you write inline remediations directly in your editor workspace. You write remediation scripts and patch your systems using live, production-level vulnerability data instead of guessing.

Verify security policies inside your editor

`list_security_policies` pulls your global cloud security rules directly into your Cursor chat. When writing Terraform or CloudFormation templates, your agent cross-references your local code against active policies to catch issues like open SSH ports before you commit. This MCP Server connection keeps your local development perfectly aligned with production rules. You avoid triggering security team alerts because your editor alerts you to compliance drift while you write the code.

Run threat hunting queries in agent mode

`execute_query` lets your Cursor agent run complex LQL threat hunting queries to inspect Kubernetes process spawn trees or anomalous login patterns. The agent analyzes the returned JSON data to verify if your code changes will resolve active runtime anomalies. You can also use `list_lql_queries` to inspect existing query templates directly from your editor. This gives you the precise cloud telemetry fields needed to write accurate policy rules without switching tabs.

Setup guide

Set up Lacework (Cloud Security & CNAPP) MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Lacework (Cloud Security & CNAPP) MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Lacework (Cloud Security & CNAPP) transactions." If the MCP tools are loaded correctly, Cursor will call the Lacework (Cloud Security & CNAPP) tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "lacework-cloud-security-cnapp-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lacework. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Lacework (Cloud Security & CNAPP) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Lacework (Cloud Security & CNAPP) MCP in Cursor

Run `list_host_vulnerabilities` within Cursor to fetch active CVEs on your EC2 or GCE virtual machines. Cursor uses this live data to suggest specific package upgrades or configuration changes directly in your active code files.

Yes, Cursor calls `search_cloud_inventory` to pull a real-time list of active cloud assets, networking perimeters, and S3 buckets. This lets the AI editor analyze your live infrastructure topology as you write deployment scripts.

Your Cursor agent uses this MCP Server to execute `list_resource_groups` to distinguish between staging and production environments defined in your policies. This ensures your automated code fixes target the correct scope without accidentally modifying critical production resources.

You create a `.cursor/mcp.json` file in your project root and add the server definition under the `mcpServers` key. Once saved, Cursor's agent mode instantly gains access to all ten cloud security tools.

Absolutely, all telemetry fetched via `get_alert` is processed inside an ephemeral, zero-trust sandbox. Vinkius never logs your raw cloud security alerts or vulnerability payloads, keeping your proprietary infrastructure data completely private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript