morse_code_convert

Morse Code Encoder / Decoder — Encode text (A-Z, 0-9) to International Morse Code, or decode Morse back to text.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp
Medium RISK CLASS
Category Write
Parameters 21 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/morse-code-convert.md

What morse_code_convert does on Gateway

AI agents use morse_code_convert to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.

ParameterTypeRequiredDescription
mode string encode | decode (default encode)
text string Yes Text to encode, or Morse to decode

Parameters from the server's own tool schema.

Why morse_code_convert is rated Medium

An AI agent can call morse_code_convert faster than any human can review: one bad instruction and it creates or modifies resources in Gateway by the hundred, each call as confident as the last.

Questions about morse_code_convert

What does the morse_code_convert tool do? +

Morse Code Encoder / Decoder — Encode text (A-Z, 0-9) to International Morse Code, or decode Morse back to text. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does morse_code_convert accept? +

morse_code_convert accepts 2 parameters: mode, text. Required: text. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on morse_code_convert? +

Register the Gateway MCP server in PolicyLayer and add a rule for morse_code_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 Gateway. Nothing to install.

What risk level is morse_code_convert? +

morse_code_convert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit morse_code_convert? +

Yes. Add a rate_limit block to the morse_code_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.

How do I block morse_code_convert completely? +

Set action: deny in the PolicyLayer policy for morse_code_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.

What MCP server provides morse_code_convert? +

morse_code_convert is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gateway, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gateway's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.