hamming_distance
Calculate Hamming distance between two equal-length strings.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hamming-distance.md
What hamming_distance does on UnClick
AI agents call hamming_distance 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 |
|---|---|---|---|
text_a | string | Yes | First string. |
text_b | string | Yes | Second string (must be same length). |
Parameters from the server's own tool schema.
Why hamming_distance is rated Low
This is a stateless algorithmic computation. It takes two inputs (strings) and returns a numeric result representing the number of positions at which the characters differ. There is no access to external data, no mutations, no execution of arbitrary code, and no financial implications. The output depends only on the mathematical properties of the input strings.
From the tool's definition Tool calculates Hamming distance between two strings—a purely mathematical/computational operation with no side effects, data retrieval, or modification.
Attacks that exploit this kind of access
The rule that runs hamming_distance 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 hamming_distance, this is the rule to start with:
hamming_distance 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 hamming_distance call is checked against it from then on.
Questions about hamming_distance
Calculate Hamming distance between two equal-length strings. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hamming_distance accepts 2 parameters: text_a, text_b. Required: text_a, text_b. 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 hamming_distance: 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.
hamming_distance 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 hamming_distance 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 hamming_distance. 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.
hamming_distance 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