metaphone_encode
Encode words using the Metaphone phonetic algorithm, optionally comparing two words.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/metaphone-encode.md
What metaphone_encode does on UnClick
AI agents call metaphone_encode 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 | string | Yes | Word(s) to encode. |
compare | string | — | Second word to compare phonetically. |
Parameters from the server's own tool schema.
Why metaphone_encode is rated Low
Metaphone encoding is a deterministic phonetic algorithm that transforms input text into phonetic codes for comparison purposes. This is a pure computational function that retrieves/generates derived data without creating, modifying, deleting, or executing arbitrary code. No blast radius from misuse.
From the tool's definition Tool description states it 'encode[s] words' and performs 'comparing two words' - both read-only operations with no side effects, data modifications, or external state changes.
Attacks that exploit this kind of access
The rule that runs metaphone_encode 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 metaphone_encode, this is the rule to start with:
metaphone_encode 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 metaphone_encode call is checked against it from then on.
Questions about metaphone_encode
Encode words using the Metaphone phonetic algorithm, optionally comparing two words. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
metaphone_encode accepts 2 parameters: text, compare. Required: 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 metaphone_encode: 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.
metaphone_encode 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 metaphone_encode 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 metaphone_encode. 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.
metaphone_encode 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