AGEX Bundle Metadata Redactor

Rewrite exposed AGEX metadata like original filename or signer ID without touching ciphertext bytes

This tool is for privacy cleanup before distribution. It lets you keep, clear, or replace visible metadata fields while leaving the encrypted payload unchanged. If the bundle was signed, the signature is removed after metadata changes because signatures cover the metadata too.

Example Results

1 examples

Remove private metadata before external sharing

Replace the original filename and clear the signer label so the recipient sees only the minimum necessary information

{
  "result": {
    "ciphertextUnchanged": true,
    "signatureStripped": true
  }
}
View input parameters
{ "bundleFile": "/public/processing/example.agex.json", "fileNameMode": "replace", "replacementFileName": "shared-file.bin", "signerIdMode": "clear" }

Click to upload file or drag and drop file here

Maximum file size: 100MB Supported formats: application/json, */*

Key Facts

Category
Security & Validation
Input Types
file, select, text
Output Type
json
Sample Coverage
4
API Ready
Yes

Overview

The AGEX Bundle Metadata Redactor allows you to sanitize and rewrite exposed metadata fields—such as the original filename, MIME type, and signer ID—within an AGEX bundle without altering the underlying encrypted ciphertext payload.

When to Use

  • •Before distributing an AGEX bundle to external partners to prevent leaking internal file naming conventions.
  • •When you need to strip sensitive signer identity labels or signatures from an encrypted package.
  • •To standardize MIME types or filenames across multiple encrypted bundles for public release.

How It Works

  • •Upload your AGEX bundle file containing the encrypted payload and exposed metadata.
  • •Select whether to keep, clear, or replace the filename, MIME type, and signer ID fields.
  • •Process the file to generate a sanitized AGEX bundle with updated metadata and stripped signatures, leaving the ciphertext bytes untouched.

Use Cases

Removing internal developer signer IDs from production-ready AGEX bundles.
Replacing sensitive original filenames with generic placeholders like 'shared-file.bin' before public distribution.
Clearing MIME type metadata to prevent third parties from identifying the underlying file format.

Examples

1. Sanitizing AGEX Bundles for External Distribution

Security Administrator
Background
An administrator needs to share an encrypted AGEX bundle externally but the bundle contains internal filenames and developer signer IDs.
Problem
The bundle exposes internal naming structures and signer identities that violate the company's privacy policy.
How to Use
Upload the AGEX bundle, set the Filename Mode to 'Replace' with 'shared-file.bin', and set the Signer ID Mode to 'Clear'.
Outcome
The metadata is updated, the signature is stripped, and the ciphertext remains completely unchanged.

2. Hiding File Format Signatures

Data Privacy Officer
Background
A privacy officer wants to distribute encrypted data without revealing the original file format through the MIME type metadata.
Problem
The MIME type field in the AGEX bundle reveals that the encrypted payload is a proprietary database format.
How to Use
Upload the AGEX bundle, set the MIME Type Mode to 'Replace' and enter 'application/octet-stream' as the replacement MIME type.
Outcome
The MIME type metadata is replaced with a generic binary stream label, preventing format identification while preserving the encrypted payload.

Try with Samples

json, text, file
Distributed Tracing Samples
Comprehensive distributed tracing examples using Jaeger, OpenTelemetry, and other modern observability tools for microservices architecture
preferred input family json
json
ELK Stack Log Analysis Samples
Comprehensive ELK Stack (Elasticsearch, Logstash, Kibana) samples for log aggregation, processing, and visualization in distributed systems
preferred input family json
json
JWT Samples
Comprehensive JWT examples from basic token structure to advanced security implementations
preferred input family json
json
PDF Samples
Generated PDF samples from tools dated 2026-02-01 to 2026-02-10
preferred input family json
json

Related Hubs

AGEX Secure File Bundle and Handoff Tools
Create encrypted AGEX bundles, inspect metadata, rotate passphrases, verify signatures, redact exposed fields, and prepare safer secure-file handoffs in one focused hub.
Text Extraction Tools
Explore 15 tools for extracting links, emails, phone numbers, dates, emojis, HTML attributes, and other structured signals from mixed text.
JSON Interchange and Format Translation Tools
Compare JSON conversion tools for CSV, YAML, TOML, GraphQL, XML, Markdown, Excel, BSON, EDN, and related structured formats in one hub.
Text Case, Encoding, and Normalization Conversion Tools
Compare text case conversion, character-width conversion, encoding conversion, quoted-printable handling, and inline text normalization tools in one hub.

FAQ

Does this tool decrypt or modify the encrypted payload?

No, the tool only modifies the unencrypted metadata fields and leaves the ciphertext bytes completely untouched.

Why is the signature removed after I edit the metadata?

Signatures cover both the metadata and the payload; modifying any metadata field invalidates the original signature, so it is stripped.

What options do I have for the metadata fields?

You can choose to keep the original value, clear it entirely, or replace it with a custom string.

Which metadata fields can I redact?

You can redact or replace the original filename, the MIME type, and the signer ID.

Does this tool support bulk processing?

This tool processes one AGEX bundle file at a time.

API Documentation

Request Endpoint

POST /en/api/tools/agex-bundle-metadata-redactor

Request Parameters

Parameter Name Type Required Description
bundleFile file (Upload required) Yes -
fileNameMode select No -
replacementFileName text No -
mimeTypeMode select No -
replacementMimeType text No -
signerIdMode select No -
replacementSignerId text No -

File type parameters need to be uploaded first via POST /upload/agex-bundle-metadata-redactor to get filePath, then pass filePath to the corresponding file field.

Response Format

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}
JSON Data: JSON Data

AI MCP Documentation

Add this tool to your MCP server configuration: 

{
  "mcpServers": {
    "elysiatools-agex-bundle-metadata-redactor": {
      "name": "agex-bundle-metadata-redactor",
      "description": "Rewrite exposed AGEX metadata like original filename or signer ID without touching ciphertext bytes",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=agex-bundle-metadata-redactor",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

Supports URL file links or Base64 encoding for file parameters.

If you encounter any issues, please contact us at [email protected]