> ## Documentation Index
> Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Crypto Toolkit

> Hash text, create HMAC signatures, and generate secure random passwords locally

The **Crypto** toolkit provides local cryptographic helpers for agents: hash text, create HMAC signatures, and generate random passwords. No API key or connection is required — operations run in EKB without calling an external service.

Add it on the agent **Toolkits** tab, then reference tools with `@` in the personality prompt.

## Prerequisites

* An agent you can edit

## Available tools

| Tool                        | Description                                                                                                                               |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Hash Text**               | Hashes a string with **MD5**, **SHA256** (default), or **SHA512**.                                                                        |
| **Generate HMAC Signature** | Signs a message with a secret key using MD5, SHA256 (default), or SHA512.                                                                 |
| **Generate Password**       | Creates a cryptographically secure random password. Length 1–256 (default 16). Character set: alphanumeric, or alphanumeric plus symbols. |

## Use cases

* Fingerprint content or file payloads before storing a checksum
* Build an HMAC for a webhook or API that expects a signed payload
* Generate one-time passwords or API-style secrets during a setup conversation

## Tips

* Prefer **SHA256** or **SHA512** for security-sensitive hashing. MD5 is available for compatibility but is not recommended for new security designs.
* The HMAC **secret** is a tool parameter for that call — do not log it or paste it into shared chats.
* Password length is capped at 256 characters.
* For storing secrets used by other integrations, prefer platform connection/vault patterns rather than keeping passwords only in chat history.

## Troubleshooting

| Symptom                       | What to check                                                                                                                               |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Unexpected hash algorithm     | Pass `md5`, `sha256`, or `sha512` explicitly; blank values default to SHA256                                                                |
| Password rejected as too long | Use length ≤ 256                                                                                                                            |
| Need file hashing from disk   | Hash the text/content you already loaded (for example via [File Helpers](/agents/toolkits/file-helpers)); this toolkit hashes string inputs |

## Related

* [File Helpers](/agents/toolkits/file-helpers)
* [Toolkits overview](/agents/toolkits/overview)
