Topic starter
30/10/2026 2:21 pm
TL;DR: Browser AI, desktop AI and coding agents now run on the endpoint, creating blind spots because EDR, web filters and network tools do not fully see prompts, local agent actions or certificate-pinned traffic, according to Cato Networks. That shifts control to endpoint-level discovery, prompt inspection and tool governance before sensitive data leaves the device.
Editorial analysis by NHI Mgmt Group, based on content published by Cato Networks: “Cato AI Endpoint secures browser AI, desktop AI and coding agents on every endpoint”.
Key questions
Q: How should security teams govern personal AI assistants that act on behalf of employees?
A: Treat each assistant as a distinct non-human actor with its own identity, policy scope, and audit trail.
Q: Why do endpoint AI agents create a security blind spot for current controls?
A: Because they operate at the OS layer and can access data without generating the browser or proxy events most security tools rely on.
Q: How should teams respond when AI agents use third-party tools and MCP connections?
A: Teams should treat those connections as access-bearing dependencies, not as ordinary integrations.
Practitioner guidance
- Establish an endpoint AI inventory Discover browser AI, desktop AI, local agents, MCP servers and skills on managed devices before trying to write policy around them.
- Block or monitor unapproved agent tools Set runtime controls so agents cannot invoke tools, skills or remote MCP servers that have not been approved for the task or user context.
- Inspect prompts at the device boundary Apply local prompt controls for copy-paste, sensitive file content and customer data before the information reaches the model or a connected service.
Bottom line: Browser AI and coding agents create a governance gap when they can read files, invoke tools and act on the user's access from the endpoint.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
30/10/2026 8:53 pm
Endpoint AI governance is now an identity problem, not only a content problem. When an AI assistant can read files, call tools and act under the user's access, the control question becomes who or what is allowed to exercise that authority on the device. That puts prompt handling, tool approval and local agent discovery into the same governance frame as privilege management. The practitioner conclusion is simple: endpoint AI needs access governance, not just content filtering.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How can organisations reduce risk from prompts containing sensitive data?
A: Move prompt inspection and blocking to the device so sensitive text can be stopped or anonymised before it reaches the model. That approach matters when users paste customer records, source code or other protected information into AI apps, especially where certificate pinning limits what the network can inspect.
👉 Read our full editorial: Endpoint controls for browser AI and coding agents on devices