# Bay MCP security: endpoint scan and on-device enforcement

URL: https://mcpservercybersecurity.com/vendors/bay/
Updated: 2026-11-16

Bay says its endpoint product finds agents, extensions, CLI tools and MCP servers on employee machines through one script run by an existing MDM or EDR, and that every MCP server is scanned for malicious indicators before approval and each time it changes. Third-party press reported that Bay Enforcer, a static binary, decides allow, ask or deny on each action on the device through a native hook, with an install under five minutes. Bay says policy follows identity-provider groups, decisions and transcripts are logged, and events reach a SIEM in OCSF format. Bay is a young company that left stealth in 2026, publishes no price and has little independent testing behind its claims. A list of MCP clients read and inspection of tool-call arguments: none found on 16 Nov 2026.

Bay is a young company that left stealth in 2026, publishes no price and has little independent testing behind its claims.

## Strength and weakness for MCP Server Security

**Strength:** Scans MCP servers for malicious indicators before approval and enforces tool-call decisions on the device (bay-26, bay-48).

**Weakness:** None found on 2026-11-16 for a list of MCP clients discovered or tool-call argument inspection (bay-71, bay-57).

## Scores and evidence

Bay is 10th in the overall ranking at 46.0 of 100. Each score below lists the fact ids behind it; the facts follow further down with their sources and read dates.

**Bay: score per criterion**

| Criterion | Score | Weight | Why | Facts |
|---|---|---|---|---|
| Discovery | 4 of 10 | 25 | The vendor claims discovery of MCP servers and names Claude Code and Cursor; a list of MCP client configurations read: none found. | [bay-14](#fact-bay-14), [bay-15](#fact-bay-15), [bay-70](#fact-bay-70), [bay-71](#fact-bay-71) |
| Vetting before use | 4 of 10 | 20 | The vendor claims scanning before approval for malicious indicators; detail and an enforced server registry: none found. | [bay-26](#fact-bay-26), [bay-27](#fact-bay-27), [bay-77](#fact-bay-77) |
| Runtime control of tool calls | 6 of 10 | 20 | Third-party press confirms local allow, ask or deny on each action via a native hook; inspection of tool-call arguments: none found. | [bay-46](#fact-bay-46), [bay-47](#fact-bay-47), [bay-54](#fact-bay-54), [bay-55](#fact-bay-55), [bay-57](#fact-bay-57) |
| Deployment | 6 of 10 | 15 | A single script through MDM or EDR, with an under-five-minute install reported by a third party; supported OS list: none found. | [bay-16](#fact-bay-16), [bay-17](#fact-bay-17), [bay-19](#fact-bay-19), [bay-21](#fact-bay-21) |
| Governance and audit | 7 of 10 | 5 | The vendor documents IdP-group policy, logged decisions, full transcripts and OCSF SIEM export, all vendor-stated. | [bay-30](#fact-bay-30), [bay-31](#fact-bay-31), [bay-61](#fact-bay-61), [bay-62](#fact-bay-62), [bay-76](#fact-bay-76) |
| Transparency | 0 of 10 | 10 | Public documentation, a published price and published research or open-source code: none found. | [bay-34](#fact-bay-34), [bay-35](#fact-bay-35), [bay-36](#fact-bay-36) |
| Proof | 7 of 10 | 5 | Third-party press confirms $50 million in funding and names customers; analyst coverage: none found. | [bay-06](#fact-bay-06), [bay-07](#fact-bay-07), [bay-08](#fact-bay-08), [bay-09](#fact-bay-09) |

## Where it ranks

| View | Rank | Total |
|---|---|---|
| [Overall ranking](/ranking/) | 10th | 46.0 |
| [An engineering organization where hundreds of developers add MCP servers to their IDEs](/best-for/many-developers/) | 10th | 49.0 |
| [A security team that needs an MCP inventory across machines this month](/best-for/fast-inventory/) | 10th | 48.0 |
| [A platform team that wants an approved list of vetted MCP servers](/best-for/approved-catalog/) | 9th | 47.5 |
| [A team whose developers run agents with shell and file access through MCP tools](/best-for/stop-tool-calls/) | 8th | 52.5 |
| [A regulated company that must show which MCP servers ran and what they did](/best-for/regulated-audit/) | 10th | 52.5 |

## Product, deployment, price and owner

- Product assessed: Bay Endpoint inventory and MCP server scanning with Agent Runtime Enforcement
- Deployment: Agentless: one script through an existing MDM or EDR runs Wave, an ephemeral binary; Bay Enforcer, a static binary, decides on the device via native hook; no proxy (vendor claims)
- Time to deploy: Under 5 minutes, as claimed by the vendor; proof of value in under 14 days (SecurityWeek quote)
- Price: none found on 2026-11-16
- Owner: Bay AI, Inc.
- Website: [bay.io](https://bay.io/?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor)

## Facts and sources

- **bay-01** (vendor): Bay AI, Inc. publishes the Bay site and states its copyright on every page.Quote: "© 2026 Bay AI, Inc. All rights reserved."Source: [bay.io](https://www.bay.io/about?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-02** (vendor): Bay says it was founded by three engineers from endpoint and API security.Quote: "Bay was founded by three engineers who spent their careers solving the hardest problems in endpoint and API security."Source: [bay.io](https://www.bay.io/about?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-03** (third-party): On 2026-11-10 Bay named its leadership: Yuval Zacharia is CEO and co-founder, Aner Morag is CPO and Boris Danilovich is VP of R&D, per SiliconANGLE.Quote: "Zacharia founded Bay with Chief Product Officer Aner Morag and Vice President of Research and Development Boris Danilovich."Source: [siliconangle.com](https://siliconangle.com/2026/11/10/ai-security-startup-bay-launches-with-50m-to-vet-agent-actions-before-they-run/), read 2026-11-16.
- **bay-04** (vendor): Bay says it was founded in 2026 and is headquartered in Tel Aviv; its press release is dated 2026-11-10.Quote: "Founded in 2026, Bay is headquartered in Tel Aviv and serves customers in the United States and Europe."Source: [bay.io](https://www.bay.io/blog/bay-emerges-from-stealth-with-50m-after-fortune-100-companies-used-its-platform-to-triple-autonomous-ai-agent-use-2?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-05** (vendor): On 2026-11-10 Bay said it had raised $50 million in total funding.Quote: "Bay has raised $50 million in total funding."Source: [bay.io](https://www.bay.io/blog/bay-emerges-from-stealth-with-50m-after-fortune-100-companies-used-its-platform-to-triple-autonomous-ai-agent-use-2?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-06** (third-party): On 2026-11-11 SecurityWeek reported Bay emerged from stealth with a $37 million Series A led by Battery Ventures plus a $13 million seed.Quote: "emerged from stealth with $50 million funding (comprising a $37 million Series A round led by Battery Ventures"Source: [securityweek.com](https://www.securityweek.com/bay-raises-50-million-to-control-what-enterprise-ai-agents-can-do/), read 2026-11-16.
- **bay-07** (third-party): On 2026-11-10 SiliconANGLE reported Micron, Wix, ClickUp and Peloton are among dozens of Bay enterprise customers.Quote: "Micron Technology Inc., Wix.com Ltd., ClickUp Inc. and Peloton Interactive Inc. are among the dozens of enterprise customers signed in the nine months since Bay was founded."Source: [siliconangle.com](https://siliconangle.com/2026/11/10/ai-security-startup-bay-launches-with-50m-to-vet-agent-actions-before-they-run/), read 2026-11-16.
- **bay-08** (third-party): The Next Web noted that Bay did not name its Fortune 100 customers or say how it measured the tripling claim, and that one named customer is also an investor.Quote: "The company did not name those customers or say how it measured the figure, and TNW has not verified it."Source: [thenextweb.com](https://thenextweb.com/news/bay-50m-ai-agent-security-stealth-battery-ventures), read 2026-11-16.
- **bay-09** (none-found): None found on 2026-11-16: independent analyst coverage of Bay (Gartner, Forrester or similar) on the Bay home page or blog.Source: [bay.io](https://bay.io/?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-10** (vendor): Bay says it is SOC 2 and ISO 27001 certified.Quote: "SOC 2 & ISO 27001 Certified"Source: [bay.io](https://www.bay.io/about?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-14** (vendor): Bay says its endpoint product finds agents, extensions, CLI tools, MCP servers, skills and models on employee devices.Quote: "Bay finds every agent, extension, CLI tool, MCP server, skill and model on employee devices."Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-15** (vendor): Bay says its first scan maps agents, MCP servers, extensions, models and skills on devices, including unapproved ones.Quote: "On the first scan, Bay maps every agent, MCP server, extension, model and skill on devices, including ones nobody approved."Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-16** (vendor): Bay says it deploys with one script through an existing MDM, with no proxy and nothing installed by users.Quote: "Bay deploys with one script through an existing MDM. It does not require a proxy to route traffic through and does not require anything to be installed by users."Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-17** (vendor): Bay says it is agentless and deploys via MDM or EDR using Wave, an ephemeral binary, with no persistent agent and no proxy.Quote: "Bay is agentless: it deploys through your existing MDM or EDR using Wave, an ephemeral binary, so there’s no persistent agent to maintain and no proxy in the path."Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-18** (vendor): Bay says the endpoint inventory appears in under 5 minutes.Quote: "Bay brings it all into view in under 5 minutes and keeps it in bounds, without slowing anyone down."Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-19** (third-party): On 2026-11-10 SiliconANGLE reported Bay installs through the customer's existing MDM or EDR and the company says it takes under five minutes.Quote: "Bay installs through the mobile device management or endpoint detection and response tools a customer already has, and the company says it takes under five minutes."Source: [siliconangle.com](https://siliconangle.com/2026/11/10/ai-security-startup-bay-launches-with-50m-to-vet-agent-actions-before-they-run/), read 2026-11-16.
- **bay-20** (third-party): On 2026-11-11 SecurityWeek quoted Bay saying a fleet deploys in under five minutes and a proof of value completes in under 14 days.Quote: "complete a proof of value in less than 14 days."Source: [securityweek.com](https://www.securityweek.com/bay-raises-50-million-to-control-what-enterprise-ai-agents-can-do/), read 2026-11-16.
- **bay-21** (none-found): None found on 2026-11-16: a list of supported operating systems for the Bay endpoint scanner, on the endpoint product page and the platform page.Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-25** (vendor): Bay lists an approval workflow for newly found AI tools; details of the workflow were not published on the page.Quote: "An approval workflow people actually use"Source: [bay.io](https://www.bay.io/shadow-ai-discovery?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-26** (vendor): Bay says every plugin, package, skill and MCP server is scanned and vetted before approval and each time it changes.Quote: "Every plugin, package, skill and MCP server is scanned and vetted before it’s approved and every time it changes."Source: [bay.io](https://www.bay.io/shadow-ai-discovery?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-27** (vendor): Bay says every agent, package, extension, MCP server and skill is scanned for malicious indicators before approval.Quote: "Every agent, package, extension, MCP server and skill is scanned for malicious indicators before its approved."Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-30** (vendor): Bay says it connects to the identity provider so policies apply to the right people and groups.Quote: "Bay connects to your identity provider, so every policy applies to the right people and groups, and keeps up as your organization changes."Source: [bay.io](https://www.bay.io/ai-governance-compliance?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-31** (vendor): Bay says policies can be scoped by IdP group, device or runtime and can set which MCP servers may read or write.Quote: "Policies can be scoped by IdP group, device or runtime, and can set which MCP servers can read or write"Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-34** (observed): Bay documentation at docs.bay.io redirects to a sign-in page and is open only to signed-in Bay users.Quote: "The Bay documentation is open only to signed-in Bay users."Source: [docs.bay.io](https://docs.bay.io/?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-35** (none-found): None found on 2026-11-16: a published price. The site has no pricing page (bay.io/pricing returns 404) and the demo page only offers a 30-minute demo.Source: [bay.io](https://www.bay.io/demo?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-36** (none-found): None found on 2026-11-16: published research, threat reports or open-source code; the Bay blog lists only two announcement posts dated 2026-11-10.Source: [bay.io](https://www.bay.io/blog?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-38** (vendor): Bay says teams run Claude Code, Codex, Gemini CLI and GitHub Copilot in cloud workspaces and that Bay covers them.Quote: "Teams now run agents like Claude Code, Codex, Gemini CLI and GitHub Copilot in clusters, cloud workspaces and hosted sessions"Source: [bay.io](https://www.bay.io/platform/cloud-workspaces?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-46** (third-party): On 2026-11-10 SiliconANGLE reported the AI tool hands each proposed action to Bay Enforcer, a static binary, through a native hook on the machine.Quote: "Each time an agent proposes an action, the AI tool running it hands the request to Bay Enforcer, a static binary, through a native hook."Source: [siliconangle.com](https://siliconangle.com/2026/11/10/ai-security-startup-bay-launches-with-50m-to-vet-agent-actions-before-they-run/), read 2026-11-16.
- **bay-47** (vendor): Bay says runtime enforcement decides allow, ask, deny or steer on every action, locally and in milliseconds with no cloud round-trip.Quote: "Bay reads each agent’s whole session to understand its intent, then decides on every action: allow, ask, deny or steer."Source: [bay.io](https://www.bay.io/agent-runtime-enforcement?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-48** (vendor): Bay says it acts on credential access, risky shell commands and untrusted MCP server connections in milliseconds.Quote: "When an agent reaches for credentials, runs a risky shell command or connects to an untrusted MCP server, Bay allows, asks, denies or steers the action in milliseconds"Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-54** (third-party): On 2026-11-11 SecurityWeek reported Bay decides in milliseconds to allow, refer to the user, redirect or deny each action.Quote: "decides in milliseconds whether to allow the action, refer it to the user, redirect it based on policy, or simply deny it"Source: [securityweek.com](https://www.securityweek.com/bay-raises-50-million-to-control-what-enterprise-ai-agents-can-do/), read 2026-11-16.
- **bay-55** (third-party): On 2026-11-10 The Next Web reported Bay checks every action an agent proposes before it runs, then allows, blocks or asks a person.Quote: "It checks every action an agent proposes before it runs, then allows it, blocks it or asks a person."Source: [thenextweb.com](https://thenextweb.com/news/bay-50m-ai-agent-security-stealth-battery-ventures), read 2026-11-16.
- **bay-57** (none-found): None found on 2026-11-16: named blocking of package installs or network calls, or inspection of tool-call arguments, on the endpoint and runtime pages.Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-58** (vendor): Bay says it applies intent-aware enforcement on every tool call in cloud agents.Quote: "Intent-aware enforcement on every tool call."Source: [bay.io](https://www.bay.io/platform/cloud-workspaces?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-61** (vendor): Bay says every decision is logged against the policy behind it for auditors.Quote: "Every decision is logged against the policy behind it, ready for your auditors."Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-62** (vendor): Bay says events reach the customer SIEM in OCSF format.Quote: "Events arrive in your SIEM in OCSF format, with enough context that analysts can triage without opening another console."Source: [bay.io](https://www.bay.io/ai-agent-investigation?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-63** (vendor): Bay says it records every prompt, tool call and system action on one timeline per session.Quote: "Every prompt, tool call and system action on one timeline, so you can see how an agent got from its first instruction to its last action."Source: [bay.io](https://www.bay.io/ai-agent-investigation?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-68** (vendor): Bay's product walkthrough says a discovered Claude Code install was connected to Salesforce, Atlassian and Sentry and could read plaintext secrets in its MCP configs.Quote: "the agent can read plaintext secrets in its MCP configs, as well as AWS and SSH keys on disk"Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-69** (vendor): Bay's product walkthrough names a Claude Code install as a discovered finding.Quote: "A Claude Code install is signed in with a personal Gmail account and connected to Salesforce, Atlassian and Sentry."Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-70** (vendor): Bay names Claude Code and Cursor as coding agents it secures on the endpoint.Quote: "How do you secure AI coding agents like Claude Code and Cursor on the endpoint?"Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-71** (none-found): None found on 2026-11-16: a list of MCP client configurations discovered (Claude Desktop, VS Code, Windsurf, JetBrains) or of remote server support, on the endpoint page.Source: [bay.io](https://www.bay.io/platform/ai-endpoint-security?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-76** (vendor): Bay says its records include full transcripts of prompts, actions and MCP calls traceable to a person.Quote: "Full transcripts of prompts, actions and MCP calls - traceable to the person behind each session."Source: [bay.io](https://www.bay.io/platform/cloud-workspaces?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.
- **bay-77** (none-found): None found on 2026-11-16: a per-server allowlist or registry for MCP servers beyond scoping which servers may read or write; see approval workflow mention.Source: [bay.io](https://www.bay.io/platform?utm_source=mcpservercybersecurity.com&utm_medium=referral&utm_campaign=vendor), read 2026-11-16.

## Related pages

- [All vendor profiles](/vendors/)
- [Backslash Security profile](/vendors/backslash-security/)
- [Cisco profile](/vendors/cisco/)
- [The ranking](/ranking/)
- [How scores are set](/method/)
- [Best tool by situation](/best-for/)
- [MCP Risk Register](/mcp-risk-register/)
- [MCP Security Checklist](/mcp-security-checklist/)
