Lasso Security MCP security: discovery, scanning and call monitoring
Lasso Security says it discovers MCP servers across the organization and inventories Claude Code, Claude Desktop, Cursor, Windsurf, Codex and OpenCode. It scores servers on permissions and descriptions, scans tool descriptions for hidden instructions, and inspects every tool call before execution with flag, block or masking options. Lasso says it keeps audit trails of every MCP connection and tool call, exports logs to a SIEM and applies role-based control per team and server. It deploys through hooks pushed by an enterprise management platform, with no agent, and an open-source gateway is published. Gaps on 16 Nov 2026: supported operating systems, deploy time, VS Code coverage, public documentation and a price are none found; capability statements are the vendor's.
Facts read on .
Strength and weakness for MCP Server Security
Strength: Documents MCP server discovery with risk scores, tool-description scanning and tool-call monitoring with SIEM export (lasso-security-19, lasso-security-21, lasso-security-25).
Weakness: No operating systems, deploy time, VS Code coverage or public docs found (lasso-security-30, lasso-security-52; none found on 2026-11-16).
Scores and evidence
Lasso Security is 7th in the overall ranking at 56.0 of 100. Each score below lists the fact ids behind it; the facts follow further down with their sources and read dates.
| Criterion | Score | Weight | Why | Facts |
|---|---|---|---|---|
| Discovery | 6 of 10 | 25 | The vendor names Claude Code, Claude Desktop, Cursor, Windsurf, Codex and OpenCode and inventories MCP servers; vendor claims only. | lasso-security-19, lasso-security-13, lasso-security-45 |
| Vetting before use | 6 of 10 | 20 | The vendor scores servers on permissions and descriptions and scans descriptions for hidden instructions; an enforced approved list: none found. | lasso-security-20, lasso-security-21 |
| Runtime control of tool calls | 6 of 10 | 20 | The vendor claims inspecting every tool call before execution on the device with flag, block or masking; vendor claims only. | lasso-security-12, lasso-security-22, lasso-security-28, lasso-security-29 |
| Deployment | 4 of 10 | 15 | Hooks deployed by the enterprise management platform with no agent; supported OS and a measured time: none found. | lasso-security-26, lasso-security-29, lasso-security-30 |
| Governance and audit | 7 of 10 | 5 | The vendor claims role-based control per team and server, audit trails of every tool call and SIEM export, all vendor-stated. | lasso-security-24, lasso-security-25 |
| Transparency | 4 of 10 | 10 | Research and an observed open-source gateway are published; a price and public documentation: none found. | lasso-security-31, lasso-security-49, lasso-security-51, lasso-security-52 |
| Proof | 7 of 10 | 5 | Third-party press confirms funding and names customers; analyst placement is a vendor claim. | lasso-security-02, lasso-security-03, lasso-security-04 |
Where it ranks
Product, deployment, price and owner
- Product assessed: Lasso MCP Security (MCP server discovery, risk scoring, tool-call monitoring) and open-source MCP Gateway
- Deployment: Agentless (read-only CI and cloud integrations), API, SDK, gateway or firewall integration, browser extension, and Claude Code lifecycle hooks via enterprise management
- Time to deploy: Lasso says start in hours, not weeks, and usage control in minutes
- Price: none found on 2026-11-16
- Owner: Lasso Security Ltd.
- Website: lasso.security
Facts and sources
lasso-security-01 (vendor): Lasso says its AI Security Platform gives enterprises visibility, control and protection across AI models, agents and apps.
Quote: "Lasso's AI Security Platform gives enterprises visibility, control, and protection across AI models, agents, and apps."
Source: lasso.security, read .
lasso-security-02 (third-party): SiliconANGLE reports that Lasso Security Ltd. was founded in 2023 by Schulman and Dror and has raised more than $37 million in total, including a $30 million round announced on 2026-09-02 led by ClearSky Advisors.
Quote: "Investors have now put more than $37 million into the company."
Source: siliconangle.com, read .
lasso-security-03 (third-party): SiliconANGLE names BMW, eToro, Fiverr and the U.S. Department of Homeland Security as Lasso customers (reported 2026-09-02).
Quote: "BMW AG is a customer, and so are eToro Group Ltd., Fiverr International Ltd. and the U.S. Department of Homeland Security."
Source: siliconangle.com, read .
lasso-security-04 (vendor): On 2026-09-15 Lasso said Latio Tech's 2026 AI Security Market Report named it a platform leader (vendor's own account of a third-party report).
Quote: "In the report, Lasso is named as one of the major Platform Leaders."
Source: lasso.security, read .
lasso-security-05 (third-party): On 2026-09-01 TechCentral (a promoted article by NEWORDER) said NEWORDER is Lasso's official partner in South Africa and that Lasso is certified to ISO 27001 and SOC 2.
Quote: "Lasso Security was founded in Tel Aviv in 2023, is certified to ISO 27001 and SOC 2, and has customers across Europe, the US and Israel."
Source: techcentral.co.za, read .
lasso-security-12 (vendor): Lasso says it inspects every coding-agent tool call before execution and flags or blocks anything outside the permitted scope.
Quote: "Lasso inspects every tool call before it is executed."
Source: lasso.security, read .
lasso-security-13 (vendor): Lasso says its coding-assistant coverage addresses agents that read codebases, execute shell commands and call MCP servers (Claude Code, Cursor, Codex, OpenCode).
Quote: "Claude Code, Cursor, and Codex read your codebase, executes shell commands, calls MCPs, and takes actions on your behalf."
Source: lasso.security, read .
lasso-security-19 (vendor): Lasso says it discovers MCP servers across the organization and inventories Claude Code, Claude Desktop, Cursor, Windsurf and custom agent connections.
Quote: "Automatically discover all MCP servers connected across your organization. Inventory Claude Code and Desktop, Cursor, Windsurf, and custom agent connections."
Source: lasso.security, read .
lasso-security-20 (vendor): Lasso says it gives each MCP server a risk score from permissions, actions and description, and lets teams manage or block high-risk servers.
Quote: "Get a risk score for each MCP according to its permissions, actions, description, and more. If an MCP server triggers a high risk score, manage or block it instantly."
Source: lasso.security, read .
lasso-security-21 (vendor): Lasso says it scans MCP tool descriptions for hidden instructions and blocks prompt injection at the connection layer.
Quote: "Scan MCP server tool descriptions for hidden instructions. Detect and block prompt injection attempts at the connection layer."
Source: lasso.security, read .
lasso-security-22 (vendor): Lasso says it monitors every MCP tool call in real time and can mask sensitive data before it reaches external servers.
Quote: "Monitor every MCP tool call in real-time to identify indirect prompt injection, memory poisoning, and other AI threats or attack techniques."
Source: lasso.security, read .
lasso-security-23 (vendor): Lasso says it detects PII, API keys and credentials shared through MCP tool calls and masks them before they reach external servers.
Quote: "Detect and monitor in real-time if PII, API keys, credentials, or any other sensitive data is shared through MCP tool calls. Mask sensitive contents before they reach external servers."
Source: lasso.security, read .
lasso-security-24 (vendor): Lasso says it enforces role-based control over which users and teams can connect to which MCP servers.
Quote: "Control which users and teams can connect to which MCP servers. Enforce role-based permissions that allow approved use cases while blocking unauthorized connections."
Source: lasso.security, read .
lasso-security-25 (vendor): Lasso says it keeps audit trails of every MCP connection and tool call and exports logs to a SIEM.
Quote: "Maintain complete audit trails of every MCP connection and tool call. Export logs to your SIEM."
Source: lasso.security, read .
lasso-security-26 (vendor): Lasso says it governs AI activity on employee endpoints agentlessly, so visibility into AI tools, coding agents and MCP connections starts on day one.
Quote: "Lasso governs AI activity on employee endpoints through an agentless approach, so security teams get visibility into AI tools, coding agents, and MCP connections from day one"
Source: lasso.security, read .
lasso-security-27 (vendor): Lasso says teams with EDR or MDM tooling can connect Lasso to that stack to extend endpoint coverage.
Quote: "Teams that already run EDR or MDM tooling can connect Lasso to that existing stack, extending endpoint coverage through infrastructure they already maintain"
Source: lasso.security, read .
lasso-security-28 (vendor): Lasso says policy enforcement happens at the execution layer on the device itself.
Quote: "Policy enforcement happens at the execution layer on the device itself, so protection holds even when an agent's activity would not otherwise pass through a monitored network path."
Source: lasso.security, read .
lasso-security-29 (vendor): Lasso says it attaches to Claude Code, Cursor and Codex through lifecycle hooks deployed by the enterprise management platform, with no agent to install.
Quote: "Lasso deploys through the enterprise management platform, so there is no agent to install and no code to change."
Source: lasso.security, read .
lasso-security-30 (none-found): None found on 2026-11-16: supported operating systems and a time to deploy for MCP discovery on developer machines, searched on the MCP security, coding assistants and endpoint pages.
Source: lasso.security, read .
lasso-security-31 (observed): Lasso publishes an open-source MCP gateway (MIT license) that intercepts requests and responses to sanitize sensitive information via plugins.
Quote: "A plugin-based gateway that orchestrates other MCPs and allows developers to build upon it enterprise-grade agents."
Source: github.com, read .
lasso-security-36 (vendor): Lasso says AI usage control deploys through a browser extension, proxy integrations and data integrations, and can be running in minutes.
Quote: "Enable full AI usage control in minutes through Lasso’s lightweight deployment paths like our browser extension, proxy integrations, and data integrations."
Source: lasso.security, read .
lasso-security-45 (vendor): On 2026-09-29 Lasso said its Claude Compliance API integration is generally available, bringing Claude Enterprise users, MCP servers and skills into its inventory.
Quote: "Today we're launching Lasso's integration with Claude's Compliance API, and it is generally available starting now."
Source: lasso.security, read .
lasso-security-47 (vendor): Lasso says it runs from the Lasso tenant and starts in hours, not weeks, with no agents or code changes.
Quote: "No agents. No code changes. No source code access. Run from the Lasso tenant and start in hours, not weeks."
Source: lasso.security, read .
lasso-security-49 (vendor): On 2026-09-17 Lasso published research on how LLM text watermarking changes refusals and agent tool calling.
Quote: "We find that it does, in both model refusal behavior and agent tool calling."
Source: lasso.security, read .
lasso-security-50 (vendor): On 2026-09-09 Lasso published a technical post on LEAP, its CPU-based guardrail, with benchmark claims.
Quote: "Introducing LEAP: CPU-based AI Security Guardrails with GPU-Class Accuracy"
Source: lasso.security, read .
lasso-security-51 (none-found): None found on 2026-11-16: a published price; the pricing URL returns a 404 page and the site routes to Book a Demo.
Source: lasso.security, read .
lasso-security-52 (none-found): None found on 2026-11-16: public product documentation; docs.lasso.security loads only a sign-in dashboard titled Lasso Security - Dashboard.
Source: docs.lasso.security, read .
lasso-security-53 (vendor): Lasso says its detection covers indirect prompt injection in files, web responses and MCP outputs before they reach the coding agent.
Quote: "detect injected payloads or hidden instructions in files, web responses, and MCP outputs before they reach the coding agent’s decision layer"
Source: lasso.security, read .