This record as markdown: /tools/io-tinyfn-tinyfn/morse-encode.md
What morse_encode does on TinyFn
AI agents call morse_encode to retrieve information from TinyFn 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 to encode to Morse code |
Parameters from the server's own tool schema.
Why morse_encode is rated Low
Encoding is a read operation: it retrieves/transforms data without modifying state, creating persistent objects, executing external code, or causing financial impact. The tool is purely computational and reversible (decode exists or could exist), making it a safe informational operation.
From the tool's definition morse_encode description states it 'Encode[s] text to Morse code' — a deterministic transformation of input data with no side effects, consistent with the server's purpose of providing '500+ deterministic tools for AI agents: math, conversion, validation,…
Attacks that exploit this kind of access
The rule that runs morse_encode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For morse_encode, this is the rule to start with:
morse_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 TinyFn, apply this rule, and every morse_encode call is checked against it from then on.
Questions about morse_encode
Encode text to Morse code. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
morse_encode accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for morse_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 TinyFn. Nothing to install.
morse_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 morse_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 morse_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.
morse_encode is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue