PRODUCT NOTES · BAY
Bay: AI endpoint control facts (2026)
Short answer
By The Device Desk · Endpoint AI Finder · Published 2026-10-11
Desk research from public vendor pages read on 27 September and 11 October 2026. Profiles follow our published method; we did not run the products.
Vendor pages read September and October 2026 · updated 2026-10-13
Where do Bay's controls sit?
- DEV Filled marker: described on the product pages we read
- DEV Hatched marker: partly described (another component, a narrower scope, or method not detailed)
- DEV Dashed marker: not in our sources (it may exist; we did not find it)
| Type | Status | What the pages say | Source |
|---|---|---|---|
| On-device control | Described | Inventories AI agents, MCP servers, tools, credentials and extensions on the device, and its Enforcer returns Allow, Ask or Deny locally on prompts, pre-tool calls and post-tool responses on supported agent surfaces. Delivered as Wave, an ephemeral binary that runs through your existing MDM or EDR. Policies can be scoped by agent, group, endpoint or device. | Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 |
| Browser extension | Not in our sources | No browser extension is described. Bay's Application Control can allow or block browsers and extensions as applications, which is a device rule, not a control on what goes into browser AI. | Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 |
| Network or SSE proxy | Not in our sources | Not described on the pages we read. | None |
| AI or MCP gateway | Not in our sources | Not described on the pages we read. | None |
| Policy only | No product needed | Policy is your own work whichever product you choose. | None |
How does Bay decide on an AI action?
| Decides on a tool call before it runs | MatchesEvaluates prompts, pre-tool calls and post-tool responses and returns Allow, Ask or Deny locally, which Bay states takes under 4ms with no cloud round-trip, on supported agent surfaces. Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 |
|---|---|
| Can warn or ask instead of only blocking | MatchesAsk is one of three answers, with Allow and Deny. Source: Bay homepage · Read 27 Sep 2026 |
| Can block an agent, tool or action | MatchesDeny stops an action. Rules cover MCP servers (an allow or block list, and per-tool rules for read, create, update, delete and execute), applications, CLIs, browsers, IDEs and extensions, credentials and files, network egress allow lists, and capability rules such as shell execution, package installation and cloud CLIs. Source: Bay blog: Ghostjacking (re-read) · Read 11 Oct 2026 |
| Has a watch-only or simulation mode | MatchesSimulation Mode runs a rule without enforcing it. Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 2026 |
How does Bay reach devices, and which AI tools does it name?
| How it reaches devices | Deploys through your existing EDR or MDM, with no new agents and no new tools; Bay says it scans in minutes and exits cleanly. Source: Bay homepage · Read 27 Sep 2026 |
|---|---|
| Rolls out through EDR or device management you run | MatchesDeploys through your existing EDR or MDM; no new agents. Source: Bay homepage · Read 27 Sep 2026 |
| Names the coding agents it covers | MatchesManaged settings for Claude Code, Codex and Claude Desktop lock permission rules, preserve managed hooks, restrict MCP servers and constrain plugin sources. Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 2026 |
| AI tools and surfaces named | AI agents, MCP servers, tools, credentials, extensions, settings and endpoint deployments, with managed settings for Claude Code, Codex and Claude Desktop. Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 2026 |
| Built into | None |
| Works with | None in our sources |
What else does Bay cover?
| Controls what goes into browser AI | Not in our sources |
|---|---|
| Records who or what took each action | MatchesRecords who triggered an action, whether a human was involved, and the chain from prompt to system action. Source: Bay homepage · Read 27 Sep 2026 |
| Also covers SaaS, cloud or homegrown AI | Not in our sources |
What does Bay cost?
Not published. Bay's site has a demo request and no pricing page (re-checked 11 October 2026).
Source: Bay homepage (re-read) · Read 11 Oct 2026
Where is Bay strong, and where are its limits?
Strengths and limits come from the product's own pages and our sources; a limit can be something we did not find.
Strengths
- Decides on each agent action before it runs: Allow, Ask or Deny on prompts, pre-tool calls and post-tool responses, using identity, prior actions and data accessed.
- Rolls out through the EDR or MDM you already run, with no new agent left on the device.
- Simulation Mode for new rules, per-tool MCP rules, and an activity record that shows who triggered an action and whether a person was involved.
Limits
- Endpoint only: no browser extension, network proxy or AI gateway is described, and nothing on SaaS or cloud-hosted AI apps.
- One of the smallest public footprints here: a single homepage, two blog posts, no documentation portal and no published pricing (re-checked 11 October 2026).
- Headline figures such as under 5 minutes to deploy, under 1% false positives and 100% of shadow AI discovered are Bay's own statements and have not been verified.
What does Bay say about itself?
What has Bay announced recently?
No dated announcements in our sources.
Bay published its Ghostjacking research in August 2026 (the page gives the month only).
Source: Bay blog: Ghostjacking, an AI agent attack (August 2026) · Read 27 Sep 2026
Who should shortlist Bay?
Consider Bay if your developers run coding agents with many MCP servers and you want a decision on each action before it runs, or if you want to add AI agent control through the EDR or MDM you already run instead of rolling out another agent.
In our example finder profiles, Bay is in the first group for: Coding agents with production access, blocking first.