AI agents call hash_md5 to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to hash |
Parameters from the server's own tool schema.
This tool performs a deterministic, read-only computation. Hashing text does not create, modify, delete, or execute any external operations—it simply transforms input into an output digest. No data is stored, no commands are executed, and no irreversible changes occur. This is categorized as Read because it retrieves/computes a derived value with no side effects.
From the tool's definition Tool name is 'hash_md5' and description states 'Generate MD5 hash of text.' MD5 is a cryptographic hash function that produces a fixed-size output from input text without modifying the original data or triggering side effects.
Attacks that exploit this kind of access
Generate MD5 hash of text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
hash_md5 accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for hash_md5: 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 TinyFn. Nothing to install.
hash_md5 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hash_md5 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_md5. 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_md5 is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
hash_md5 is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →