hash_compare
Compare text against an expected hash to verify integrity.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hash-compare.md
What hash_compare does on UnClick
AI agents call hash_compare to retrieve information from UnClick 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 |
|---|---|---|---|
hash | string | Yes | Expected hash value. |
text | string | Yes | Text to hash and compare. |
algorithm | string | — | Hash algorithm (default: sha256). |
Parameters from the server's own tool schema.
Why hash_compare is rated Low
Hash comparison is a read-only operation that queries cryptographic state without mutation. The tool accepts input text and a hash, performs a comparison, and returns a result. No data is altered, no commands are executed, and no external systems are triggered. This is classic Read category behavior.
From the tool's definition Tool description states 'Compare text against an expected hash to verify integrity.' This is a verification/comparison operation with no side effects—it reads and compares data without creating, modifying, executing, deleting, or moving anything.
Attacks that exploit this kind of access
The rule that runs hash_compare 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 hash_compare, this is the rule to start with:
hash_compare 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 UnClick, apply this rule, and every hash_compare call is checked against it from then on.
Questions about hash_compare
Compare text against an expected hash to verify integrity. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hash_compare accepts 3 parameters: hash, text, algorithm. Required: hash, text. 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 hash_compare: 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.
hash_compare 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_compare 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_compare. 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_compare is provided by the UnClick MCP server (@unclick/mcp-server). 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.
This server
Across the catalogue