AI agents invoke pager_stop_decoding 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 triggers an external operation (halting an active SDR decoding process) rather than simply querying or retrieving data. While stopping a process is less severe than starting one, it still represents execution of a command that controls hardware/radio state. It is not destructive (no data loss), not financial, and not a simple read operation.
From the tool's definition Tool name 'pager_stop_decoding' and description 'Stop decoding POCSAG pager messages' indicate control of an active radio decoding operation. It stops an ongoing process whose effects depend on the prior state of the radio receiver.
Documented attack patterns abuse exactly the kind of access pager_stop_decoding 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 pager_stop_decoding:
{
"version": "1",
"default": "deny",
"tools": {
"pager_stop_decoding": {
"limits": [
{
"counter": "pager_stop_decoding_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pager_stop_decoding 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.
Stop decoding POCSAG pager messages. 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 pager_stop_decoding: 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.
pager_stop_decoding 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 pager_stop_decoding 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 pager_stop_decoding. 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.
pager_stop_decoding 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.