morse_timing

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/morse-timing.md

WHAT IT DOES

What morse_timing does on ScorpTech x402 API

AI agents call morse_timing to retrieve information from ScorpTech x402 API 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
`wpm`	integer	—
`text`	string	Yes

Parameters from the server's own tool schema.

RISK

Why morse_timing is rated Low

Even though morse_timing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs morse_timing safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For morse_timing, this is the rule to start with:

morse_timing Allowed

morse_timing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "morse_timing": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every morse_timing call is checked against it from then on.

FAQ

Questions about morse_timing

What does the morse_timing tool do? +

How long a Morse message takes at a given speed. The dit is 1200/wpm milliseconds. PARIS is 43 units, or 50 units once the trailing 7-unit word gap of a stream is added. SOS is 27 units. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/morse-timing. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does morse_timing accept? +

morse_timing accepts 2 parameters: wpm, 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_timing? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for morse_timing: 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 ScorpTech x402 API. Nothing to install.

What risk level is morse_timing? +

morse_timing is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit morse_timing? +

Yes. Add a rate_limit block to the morse_timing 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_timing completely? +

Set action: deny in the PolicyLayer policy for morse_timing. 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_timing? +

morse_timing is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →