hash_text
utilpeek: Hash text or bytes: sha256, keccak256, blake2b, md5, crc32, ... For a keyed HMAC use hmac_sign_verify. Returns hex digests of the text (as UTF-8) or base64 bytes you send. md5 and sha1 are for checksums, not security. Send exactly one of text or base64 (else 422 invalid_request); bad ba...
This record as markdown: /tools/dev-tanod-tanod/hash-text.md
What hash_text does on Tanod
AI agents use hash_text to create or update resources in Tanod, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tanod environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | object | — | Text, hashed as UTF-8 (at most 1 MB); send text OR base64. |
base64 | object | — | Raw bytes as standard base64 (at most 1 MB decoded); send text OR base64. |
algorithms | array | — | Any of md5, sha1, sha256 (default), sha512, sha3_256, blake2b, keccak256, crc32. |
Parameters from the server's own tool schema.
Why hash_text is rated Medium
An AI agent can call hash_text faster than any human can review: one bad instruction and it creates or modifies resources in Tanod by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs hash_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hash_text, this is the rule to start with:
hash_text stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every hash_text call is checked against it from then on.
Questions about hash_text
utilpeek: Hash text or bytes: sha256, keccak256, blake2b, md5, crc32, ... For a keyed HMAC use hmac_sign_verify. Returns hex digests of the text (as UTF-8) or base64 bytes you send. md5 and sha1 are for checksums, not security. Send exactly one of text or base64 (else 422 invalid_request); bad base64 is a 422 invalid_base64. The input is never echoed. Typically under 0.1 s (keccak256 about 2 s per MB). Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/hash-text-api.html. It is categorised as a Write tool in the Tanod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hash_text accepts 3 parameters: text, base64, algorithms. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for hash_text: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tanod. Nothing to install.
hash_text is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hash_text rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for hash_text. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
hash_text is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue