util_hash
Hash a string with SHA-256, SHA-1, or MD5. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.
This record as markdown: /tools/delx-delx-mcp/util-hash.md
What util_hash does on Delx MCP Server
AI agents call util_hash to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | — | String to hash |
algorithm | string | — | Hash algorithm |
Parameters from the server's own tool schema.
Why util_hash is rated Low
Hashing is a read-only cryptographic operation that transforms input to output without creating, modifying, deleting, or executing anything. It does not retrieve data from a system, but rather performs a pure computational function. The mention of 'x402 utility pricing' is a billing concern, not a functional capability that changes the security categorization.
From the tool's definition Tool description states it 'Hash[es] a string with SHA-256, SHA-1, or MD5' - a cryptographic hash operation that takes input and produces a deterministic output without side effects, data modification, or external operations.
Attacks that exploit this kind of access
The rule that runs util_hash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_hash, this is the rule to start with:
util_hash is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every util_hash call is checked against it from then on.
Questions about util_hash
Hash a string with SHA-256, SHA-1, or MD5. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_hash accepts 2 parameters: input, algorithm. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_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 Delx MCP Server. Nothing to install.
util_hash 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 util_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 util_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.
util_hash is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue