AI agents invoke marine_stop_tracking 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 command to terminate an active tracking operation on a hardware device (SDR). While stopping a process is typically reversible, it is an Execute action that actively controls external hardware state and interrupts ongoing operations. It is not a simple Read (no data retrieval), not Write (not creating/modifying persistent data), and not Destructive (the tracking can be restarted).
From the tool's definition Tool name 'marine_stop_tracking' and description 'Stop tracking ships' indicate an active operation that halts an ongoing tracking process. The server context shows this is part of SDR (Software Defined Radio) control for real-time signal analysis.
Documented attack patterns abuse exactly the kind of access marine_stop_tracking 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_stop_tracking:
{
"version": "1",
"default": "deny",
"tools": {
"marine_stop_tracking": {
"limits": [
{
"counter": "marine_stop_tracking_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}marine_stop_tracking 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 tracking ships. 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_stop_tracking: 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_stop_tracking 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_stop_tracking 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_stop_tracking. 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_stop_tracking 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.