Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

Security

AES Encryption Tool

Encrypt or decrypt text and files with AES-256-GCM and export IV-based bundles

json· JSON resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL
# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/aes-encryption-tool' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"fileInput.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/aes-encryption-tool' \
  -F 'inputType=text' \
  -F 'operation=decrypt' \
  -F 'textInput={"algorithm":"aes-256-gcm","encoding":"base64","salt":"c2FsdC1mb3ItYWVzLXRvb2w=","iv":"AQIDBAUGBwgJCgsM","authTag":"1VBqj1TTlms/dNQoH4WMGA==","ciphertext":"h4VrXvk="}' \
  -F 'fileInput=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'secretKey=test-key-123' \
  -F 'outputEncoding=base64'

© 2026 Elysia Tools. Developer documentation.

Back to siteBrowse tools

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/aes-encryption-tool

Parameters

NameTypeRequiredDescription
inputTypeselectYes—
operationselectYes—
textInputtextareaNo—
fileInputfileupload requiredNo—
secretKeytextYes—
outputEncodingselectYes—
File-type parameters must be uploaded first via POST /upload/aes-encryption-tool, 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-aes-encryption-tool": {
      "name": "aes-encryption-tool",
      "description": "Encrypt or decrypt text and files with AES-256-GCM and export IV-based bundles",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=aes-encryption-tool",
      "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": "aes-encryption-tool",
    "arguments": {
  "inputType": "text",
  "operation": "decrypt",
  "textInput": "{\"algorithm\":\"aes-256-gcm\",\"encoding\":\"base64\",\"salt\":\"c2FsdC1mb3ItYWVzLXRvb2w=\",\"iv\":\"AQIDBAUGBwgJCgsM\",\"authTag\":\"1VBqj1TTlms/dNQoH4WMGA==\",\"ciphertext\":\"h4VrXvk=\"}",
  "fileInput": "https://example.com/file.ext",
  "secretKey": "test-key-123",
  "outputEncoding": "base64"
}
  }
}
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]

Browse tools
Open tool