Can an over-permissioned AI agent leak customer data?
Yes, and without anyone intending it. An agent with access to a CRM, a mailbox or a shared drive can be asked, or tricked through an instruction hidden in a document, an e-mail or a web page it reads, to summarise, forward or upload data far beyond what its task needs. Common routes are an agent that answers external messages and includes internal data in the reply, an agent that can send e-mail or post to external services, a coding agent that pushes code with embedded secrets to a public repository, and an agent whose logs or memory keep customer data where nobody expects it. The fix is scope: only the data the task needs, no outbound channels unless required, human approval before anything leaves the company, and separation between agents that read untrusted content and those that hold sensitive access. Test these paths before go-live. On every plan, NetSenX detects unusual outbound data volume from a host, whatever process caused it, and from the Pro plan it shows which AI services the host talks to; it does not see what the agent sent.