unclick_hash
Compute a cryptographic hash (MD5, SHA1, SHA256, SHA512) of text.
This record as markdown: /tools/creativelead-unclick/unclick-hash.md
What unclick_hash does on UnClick
AI agents invoke unclick_hash to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | |
algorithm | string | — |
Parameters from the server's own tool schema.
Why unclick_hash is rated High
The tool performs a computation (hashing) on input text. It doesn't read external data, write or modify state, delete anything, or involve finances. It executes a cryptographic function locally on provided input. Severity is low since hashing is a one-way, non-destructive, non-persistent operation with minimal blast radius.
From the tool's definition Compute a cryptographic hash (MD5, SHA1, SHA256, SHA512) of text
Attacks that exploit this kind of access
The rule that runs unclick_hash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unclick_hash, this is the rule to start with:
unclick_hash stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every unclick_hash call is checked against it from then on.
Questions about unclick_hash
Compute a cryptographic hash (MD5, SHA1, SHA256, SHA512) of text. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
unclick_hash accepts 2 parameters: text, algorithm. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for unclick_hash: 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 UnClick. Nothing to install.
unclick_hash is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unclick_hash 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 unclick_hash. 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.
unclick_hash is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue