morse_convert
Encode text to Morse code or decode Morse code to text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/morse-convert.md
What morse_convert does on UnClick
AI agents call morse_convert 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 | Text or Morse code to convert. |
Parameters from the server's own tool schema.
Why morse_convert is rated Low
This tool performs a stateless text transformation (encoding/decoding) with no side effects, no data storage, no external calls, and no destructive or financial implications. It purely converts input to output, making it a Read/transform operation with minimal risk.
From the tool's definition Encode text to Morse code or decode Morse code to text
Attacks that exploit this kind of access
The rule that runs morse_convert 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 morse_convert, this is the rule to start with:
morse_convert 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 morse_convert call is checked against it from then on.
Questions about morse_convert
Encode text to Morse code or decode Morse code to text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
morse_convert accepts 1 parameter: text. 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 morse_convert: 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.
morse_convert 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 morse_convert 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 morse_convert. 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.
morse_convert 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