This record as markdown: /tools/io-github-kivanccakmak-yaver/hash.md
What hash does on Yaver
AI agents call hash to retrieve information from Yaver 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 | Yes | Text to hash |
algorithm | string | — | md5 or sha256 (default: sha256) |
Parameters from the server's own tool schema.
Why hash is rated Low
Hashing is a pure computational function with no side effects. It takes input text and produces a deterministic output without creating, modifying, deleting, or executing anything. While it is technically a computational operation, it does not fall under Execute (which involves code/command execution with external effects) or any higher severity category.
From the tool's definition Tool description states 'Hash text with MD5 or SHA256.' Hashing is a one-way cryptographic operation that reads input text and produces a digest; it performs no modification of data, creates no side effects, and does not retrieve or modify external state.
Attacks that exploit this kind of access
The rule that runs hash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hash, this is the rule to start with:
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 Yaver, apply this rule, and every hash call is checked against it from then on.
Questions about hash
Hash text with MD5 or SHA256. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
hash accepts 2 parameters: input, algorithm. Required: input. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for 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 Yaver. Nothing to install.
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 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 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.
hash is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue