AWS describes a Skyflow interceptor for Amazon Bedrock AgentCore Gateway that handles sensitive data at two points in the gateway flow. One AWS Lambda function intercepts requests before a tool call and responses before the agent receives a tool’s reply. The design has three distinct modes: shielding tool arguments, routing model traffic through the gateway, and replacing a signed document URL with a link to a de-identified copy. AWS published its implementation guide on November 19, 2026.
A token is a substitute value that can stand in for sensitive information. In the modes AWS describes, Skyflow’s services replace selected data with tokens, and some tokens can later be mapped back to their original values. The important distinction is the path the data takes: protecting tool arguments does not automatically cover model calls or documents.
Match the protection mode to the data path: tool arguments, model requests, and signed document URLs have different requirements.
How the three modes handle data
AWS describes three modes for different points in an agent workflow. The table summarizes their purpose, routing, and key limits.
| Mode | Data path handled | How it works or what it requires | Relevant limit |
| Shield the tool | Sensitive arguments sent to a tool | Replaces sensitive argument values with reversible vault tokens; echoed values can be restored before the agent reads the tool’s reply. | The tool receives tokenized values rather than the original sensitive values. |
| Shield the model | Prompts, conversation history, files, and tool results sent to a model | Routes model calls through an AgentCore Gateway inference endpoint; the design restores only tokens created for that call. | The model client must use the gateway inference endpoint. |
| Shield the document | A document supplied through a signed URL | Replaces the signed URL with a link to a de-identified copy; AWS says Skyflow Detect fetches the document directly rather than sending its bytes through Lambda. | AWS describes signed-URL processing with Skyflow Detect v2 as a preview, with file size and processing time bounded by configuration and the gateway connection window. |
For a tool that does not need a person’s real identity to do its job, tokenizing the arguments can keep those original values out of the tool request. Model shielding addresses a different route: it applies only when the model client sends calls through the gateway’s inference endpoint. Document shielding changes the link the agent receives, rather than relying on the tool-call or model-call path alone.
AWS also describes the interceptor as failing closed when de-identification cannot be completed and restricting document handling to configured allowed locations. In the guide’s account, AgentCore Policy governs whether an agent may take an action, while the interceptor handles sensitive data in permitted traffic; Amazon Bedrock Guardrails addresses content safety and sensitive-information redaction for model interactions.
Document formats determine whether tokens can be reversed
AWS lists TXT, JSON, CSV, XML, JSONL, DOCX, XLSX, and PPTX as formats that use reversible vault tokens. For PDFs and images, it describes one-way tokens, so the original values cannot be restored from those files. That difference matters when a workflow needs the original values back: the file format affects whether this design can provide that recovery.
What the repository changes add to the picture
SkyflowFoundry’s project pull requests describe implementation details that are not captured by the high-level mode comparison. PR #14 reported earlier weaknesses in file-URL validation, including URL-pattern handling and checks around the size probe. The pull request describes tighter HTTPS, host, and path validation and a restricted probe; its page marks the change as merged. (PR #14)
PR #15 reported that HTTP-shaped events without MCP tool framing could pass without inspection. It also said the repository’s then-current targets were MCP or Lambda targets and characterized the issue as a configuration guardrail. The PR describes a default-block change and marks it merged. (PR #15)
PR #18 reported that a later agentcore deploy could remove the gateway’s interceptor configuration. It describes a change to preserve the attachment and marks that change as merged; it also specifies deploying the interceptor stack before agentcore deploy. (PR #18)
Together, those repository reports make deployment checks part of the practical picture: review how file URLs are validated, whether the target event shape is inspected or blocked, and whether gateway updates preserve the interceptor attachment.