How to give an AI agent customer context without exposing PII
Cohorts, segments and LTV all come from a pseudonymous ID. An agent almost never needs a name, email, phone number or address to answer them.
7 min read
#data-security
6 articles
Which AI agents can reach your data? Building the agent and MCP permission inventory
No console lists every AI agent touching your data. An MCP permission inventory needs seven columns and a monthly and quarterly review.
9 min read
One AI agent, many client accounts: how to keep tenant data apart
When one agent serves many tenants, data rarely leaks through an attack. It leaks via leftover context, a cache keyed without the tenant, or one shared token.
8 min read
AI data governance: what the policy has to cover once an agent reads customer data
AI data governance decides what a model may read, not just who may use it. Five questions cover it: scope, isolation, retention, audit trail, metrics.
8 min read
MCP security for marketing data: read-only, scopes, and the permission you shouldn't grant
Google's Ads MCP server is read-only, yet its OAuth scope can edit and delete your account. For ad data, MCP risk lives in the token's scope.
9 min read
Prompt injection through marketing data: the fields nobody validates
A Google Ads campaign name takes 256 characters with no documented content validation. Meta documents no maximum at all.
8 min read