Generate and transmit a signal (HackRF only)
AI agents invoke signal_generator to trigger actions in AetherLink SDR MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes radio signal transmission, which is an irreversible operation affecting the electromagnetic environment. It triggers hardware to emit RF signals whose effects depend on arguments (frequency, power, modulation). While not destructive of data and not financial, transmission of unauthorized signals could violate spectrum regulations, interfere with communications, or cause physical harm.
From the tool's definition Tool description states 'Generate and transmit a signal (HackRF only)' - transmitting signals via hardware is an external operation with real-world effects that depend on frequency and modulation arguments provided by the caller.
Documented attack patterns abuse exactly the kind of access signal_generator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AetherLink SDR MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for signal_generator:
{
"version": "1",
"default": "deny",
"tools": {
"signal_generator": {
"limits": [
{
"counter": "signal_generator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}signal_generator stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate and transmit a signal (HackRF only). It is categorised as a Execute tool in the AetherLink SDR MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AetherLink SDR MCP server in PolicyLayer and add a rule for signal_generator: 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 AetherLink SDR MCP. Nothing to install.
signal_generator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the signal_generator 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 signal_generator. 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.
signal_generator is provided by the AetherLink SDR MCP server (n-erickson/aetherlink-sdr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AetherLink SDR MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 AetherLink SDR MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.