The interceptor runs as an AWS Lambda function attached to the gateway's request and response points. It calls Skyflow Detect to find entities such as names, email addresses, phone numbers and card numbers, and swaps them for tokens. Skyflow Vault keeps the original values so authorized systems can reverse reversible tokens.
Each tool is assigned one of three modes: Shield the tool, Shield the model, or Shield the document. Shield the document swaps a signed URL for a link to a de-identified copy of the file, so the agent never reads the original. The policy lives in AWS Systems Manager Parameter Store and can change without redeploying.
If de-identification cannot finish, the call is withheld rather than sent in the clear. Document de-identification uses Skyflow Detect v2, which is in preview. The AWS post notes that PDFs and images receive one-way tokens, so their original values cannot be restored.
Why it matters if you build agents
Developers can add data protection to every tool behind a gateway without changing agent or tool code. This covers tools such as web search and document stores that otherwise receive customer data in their queries and results.
Teams should check the preview status of document de-identification and the AgentCore Gateway Region availability before deploying. Start with one workflow and watch the interceptor's CloudWatch metrics before widening the rollout.
Get stories like this every weekday
One short email with the day's agent tooling news.