Security

AGEX Bundle Metadata Redactor

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

json· JSON resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/agex-bundle-metadata-redactor' \
  -F 'file=@/path/to/bundleFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/agex-bundle-metadata-redactor' \
  -F 'bundleFile=/public/processing/example.agex.json' \
  -F 'fileNameMode=replace' \
  -F 'replacementFileName=shared-file.bin' \
  -F 'mimeTypeMode=keep' \
  -F 'replacementMimeType=application/octet-stream' \
  -F 'signerIdMode=clear' \
  -F 'replacementSignerId=distribution-key'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/agex-bundle-metadata-redactor

Parameters

Name	Type	Required	Description
bundleFile	fileupload required	Yes	—
fileNameMode	select	No	—
replacementFileName	text	No	—
mimeTypeMode	select	No	—
replacementMimeType	text	No	—
signerIdMode	select	No	—
replacementSignerId	text	No	—

File-type parameters must be uploaded first via POST /upload/agex-bundle-metadata-redactor, then the returned filePath is passed to the corresponding file field.

Response format

JSON result

JSON

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

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "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://api.elysiatools.com/mcp/sse?toolId=agex-bundle-metadata-redactor",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "agex-bundle-metadata-redactor",
    "arguments": {
  "bundleFile": "/public/processing/example.agex.json",
  "fileNameMode": "replace",
  "replacementFileName": "shared-file.bin",
  "mimeTypeMode": "keep",
  "replacementMimeType": "application/octet-stream",
  "signerIdMode": "clear",
  "replacementSignerId": "distribution-key"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]