echo_beacon

Check voice/TTS API status (0 sats/call; free tier 100 calls/mo)

SERVERHyperion SOURCEhttps://hyperion.thetempleofdoom.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-thetempleofdoom-hyperion-hyperion/echo-beacon.md

WHAT IT DOES

What echo_beacon does on Hyperion

AI agents call echo_beacon to retrieve information from Hyperion without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why echo_beacon is rated Low

Even though echo_beacon 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 echo_beacon safely

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

echo_beacon Allowed

echo_beacon 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": {
    "echo_beacon": {}
  }
}

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

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

FAQ

Questions about echo_beacon

What does the echo_beacon tool do? +

Check voice/TTS API status (0 sats/call; free tier 100 calls/mo). It is categorised as a Read tool in the Hyperion MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on echo_beacon? +

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

What risk level is echo_beacon? +

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

Can I rate-limit echo_beacon? +

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

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

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

KEEP EXPLORING

More on Hyperion, and thousands of servers like it.

This server

All 355 Hyperion tools →

Across the catalogue

The MCP Attack Database →

Guides

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