enclave-ingress-filter

Name: enclave-ingress-filter
Availability: InStock
Author: Latch

Filter sensitive content from HTTP responses using regex patterns.

2|Updated Feb 26, 2026

Search Tags:#data security #api security #http filtering #content redaction #metadata tokenization

Ready to run

npx skills add https://github.com/latchagent/latch-core --skill enclave-ingress-filter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enclave-ingress-filter
Source: https://github.com/latchagent/latch-core/tree/main/.agents/skills/enclave-ingress-filter
Command: npx skills add https://github.com/latchagent/latch-core --skill enclave-ingress-filter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Enclave Ingress Filter Skill mitigates data exposure risks by filtering sensitive content from HTTP responses before they are processed by the agent.

Core Features & Use Cases

Content-Type Classification: Identifies and scans response bodies for sensitive data based on Content-Type.
Scanning Pipeline: Implements a regex-based scanning process to identify and redact sensitive information.
Token Same-Origin: Ensures that tokens are de-tokenized only when sent back to the originating service.
Use Case: Ideal for ensuring compliance with data privacy regulations and preventing unauthorized data exfiltration.

Quick Start

Use the enclave-ingress-filter skill to scan the response body of an HTTP request and apply redactions if necessary.

Frequently Asked Questions about enclave-ingress-filter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I filter sensitive data from HTTP API responses?▼

You filter sensitive data from HTTP API responses by applying a regex-based scanning pipeline that identifies and redacts confidential information before the agent processes it. This method supports JSON and XML content types to ensure data privacy.

How does metadata tokenization work for secure HTTP content redaction?▼

Metadata tokenization for HTTP content redaction works by replacing sensitive response data with tokens bound to origin service metadata. These tokens are securely de-tokenized only when returned to the originating service, preventing unauthorized data exfiltration.

Can I use content redaction for JSON and XML web service APIs?▼

Yes, you can apply content redaction for JSON and XML web service APIs. The filtering pipeline classifies response bodies by Content-Type and applies regex pattern matching to redact sensitive information across both formats.

What is the best way to ensure data privacy compliance for web service API responses?▼

The best way to ensure data privacy compliance for web service API responses is to implement an ingress filtering mechanism that redacts sensitive content and enforces same-origin tokenization. This mitigates data exposure risks before responses are processed.

Does same-origin tokenization prevent unauthorized data exfiltration in API responses?▼

Yes, same-origin tokenization prevents unauthorized data exfiltration by ensuring tokens are de-tokenized only when sent back to the originating service. This mechanism secures sensitive data intercepted during HTTP response processing.