AI agents call morse_decode to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
morse | string | Yes | Morse code to decode |
Parameters from the server's own tool schema.
This is a pure data transformation utility that decodes Morse code into readable text. It performs no creation, modification, deletion, code execution, or financial operations. It matches the 'Read' category as a data query/transformation tool with no side effects. Severity is low as misuse cannot cause harm beyond potentially decoding unintended Morse sequences.
From the tool's definition Tool name 'morse_decode' and description 'Decode Morse code to text' indicate a deterministic conversion operation that retrieves/transforms input data without side effects.
Attacks that exploit this kind of access
Decode Morse code to text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
morse_decode accepts 1 parameter: morse. Required: morse. 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_decode: 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_decode 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_decode 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_decode. 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_decode 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.
morse_decode is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →