2,500+ MCP servers ready to use
Vinkius

Lacework (Cloud Security & CNAPP) MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Lacework (Cloud Security & CNAPP) and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "lacework-cloud-security-cnapp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Lacework (Cloud Security & CNAPP)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Lacework (Cloud Security & CNAPP) MCP Server

Connect your Lacework (FortiCNAPP) account to any AI agent and take full control of your cloud security posture and threat hunting through natural conversation.

GitHub Copilot Agent mode brings Lacework (Cloud Security & CNAPP) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Alert Orchestration — Search and retrieve deep behavioral telemetry for security alerts, identifying anomalous Kubernetes executions or AWS IAM brute-forcing attempts directly from your agent
  • Vulnerability Management — List critical CVEs executing on cloud hosts and monitor static image vulnerabilities in your container registries (ECR, DockerHub)
  • Emergency Incident Response — Instantly search your entire infrastructure for specific CVE exposure (e.g., Log4j) to identify vulnerable nodes during zero-day events
  • Asset Inventory Audit — Query the real-time cloud control-plane to enumerate running instances, unrestricted S3 buckets, and active networking perimeters
  • Threat Hunting (LQL) — Execute specialized Lacework Query Language (LQL) requests to analyze vast datasets for anomalous login patterns or API key abuse
  • Compliance Monitoring — List and audit global cloud security policies to ensure your infrastructure remains within regulatory and organizational norms

The Lacework (Cloud Security & CNAPP) MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Lacework (Cloud Security & CNAPP) to VS Code Copilot via MCP

Follow these steps to integrate the Lacework (Cloud Security & CNAPP) MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Lacework (Cloud Security & CNAPP)

Ask Copilot: "Using Lacework (Cloud Security & CNAPP), help me..."10 tools available

Why Use VS Code Copilot with the Lacework (Cloud Security & CNAPP) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Lacework (Cloud Security & CNAPP) through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Lacework (Cloud Security & CNAPP) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Lacework (Cloud Security & CNAPP) MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Lacework (Cloud Security & CNAPP) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Lacework (Cloud Security & CNAPP) to VS Code Copilot via MCP:

01

execute_query

Produces bespoke output matrices tracking API keys bypassing IAM logic, anomalous login patterns, or Kubernetes process spawn trees. Execute an LQL Threat Hunting Query on-demand

02

get_alert

Extracts precisely what baseline behavior was deviated from, providing deep contextual metadata such as explicit AWS Accounts involved, offending Container Image SHAs, and correlated external IP anomalies. Get exact behavioral payloads and telemetry for an Alert

03

list_container_vulnerabilities

Examines ECR/DockerHub registries or direct cluster deployments for images carrying critical inherited CVEs at the filesystem level before CI/CD promotion blocks. List static image vulnerabilities detected in Container Registries

04

list_host_vulnerabilities

Identifies running processes strictly matched against Critical or High CVEs (e.g., Log4j, Polkit) directly active inside EC2 or GCE instances. List known vulnerabilities executing natively on Cloud Hosts/VMs

05

list_lql_queries

These extract precise cloud telemetry fields mapping user-defined compliance checks directly against the underlying dataset. List all Lacework Query Language (LQL) structures

06

list_resource_groups

Helps define what constitutes "Production" vs "Staging" in Policy evaluation engines. List logical Resource Groups managing Lacework architectures

07

list_security_policies

Confirms whether Lacework will alert directly if an engineer violates structural norms (e.g., exposing port 22 directly to 0.0.0.0/0). List all global Cloud Security Policies enforced by Lacework

08

search_alerts

Fetches events mapping to anomalous Kubernetes executions, AWS IAM brute-forcing attempts, and massive container network exfiltrations spanning the specified time filter. Search Cloud Security alerts dynamically across Lacework

09

search_cloud_inventory

Used to dynamically enumerate running instances, active networking perimeters, or unrestricted S3 buckets discovered by cross-account role polling. Query the real-time Lacework Cloud Control-Plane Asset Inventory

10

search_cve_exposure

Directly filters the entire cloud infrastructure footprint determining exactly which specific nodes (Machines) are currently vulnerable to the designated CVE (e.g. "CVE-2026-0001"). Search all integrated Machines/Instances for a specific CVE

Example Prompts for Lacework (Cloud Security & CNAPP) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Lacework (Cloud Security & CNAPP) immediately.

01

"Search for all Critical alerts from the last 24 hours"

02

"List all host vulnerabilities for our Production resource group"

03

"Are there any unrestricted S3 buckets currently visible in our inventory?"

Troubleshooting Lacework (Cloud Security & CNAPP) MCP Server with VS Code Copilot

Common issues when connecting Lacework (Cloud Security & CNAPP) to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Lacework (Cloud Security & CNAPP) + VS Code Copilot FAQ

Common questions about integrating Lacework (Cloud Security & CNAPP) MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Lacework (Cloud Security & CNAPP) to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.