Start tracking ships via AIS on 161.975 MHz or 162.025 MHz
AI agents invoke marine_track_vessels 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 a continuous signal monitoring and decoding operation on marine AIS frequencies. While it is read-oriented in intent (gathering vessel tracking data), the mechanism is an active execution of radio tuning and tracking logic that must be managed (started/stopped).
From the tool's definition Tool 'marine_track_vessels' performs an ongoing external operation ('Start tracking ships via AIS') that actively monitors and processes radio signals on specific marine frequencies (161.975 MHz and 162.025 MHz), which constitutes triggering and maintaining…
Documented attack patterns abuse exactly the kind of access marine_track_vessels 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 marine_track_vessels:
{
"version": "1",
"default": "deny",
"tools": {
"marine_track_vessels": {
"limits": [
{
"counter": "marine_track_vessels_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}marine_track_vessels 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.
Start tracking ships via AIS on 161.975 MHz or 162.025 MHz. 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 marine_track_vessels: 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.
marine_track_vessels 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 marine_track_vessels 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 marine_track_vessels. 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.
marine_track_vessels 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.