AI agents use sdr_set_frequency to create or update resources in AetherLink SDR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AetherLink SDR MCP environment.
This tool changes the tuning frequency of the Software Defined Radio hardware. It is a Write operation because it modifies a device configuration parameter. Misuse could cause the SDR to tune to unintended frequencies, potentially intercepting communications on sensitive bands, but it does not execute code or destroy data.
From the tool's definition 'Set SDR center frequency in Hz' — modifies the operating parameter (center frequency) of the SDR hardware
Documented attack patterns abuse exactly the kind of access sdr_set_frequency 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 sdr_set_frequency:
{
"version": "1",
"default": "deny",
"tools": {
"sdr_set_frequency": {
"limits": [
{
"counter": "sdr_set_frequency_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sdr_set_frequency stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set SDR center frequency in Hz. It is categorised as a Write tool in the AetherLink SDR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AetherLink SDR MCP server in PolicyLayer and add a rule for sdr_set_frequency: 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.
sdr_set_frequency is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sdr_set_frequency 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 sdr_set_frequency. 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.
sdr_set_frequency 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.