Low Risk

marine_get_vessels

Get list of tracked vessels

How to control marine_get_vessels ↓

What marine_get_vessels does on AetherLink SDR MCP

AI agents call marine_get_vessels to retrieve information from AetherLink SDR MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why marine_get_vessels needs a policy

This tool retrieves/queries a list of currently tracked maritime vessels. The use of 'get' and the passive nature of listing tracked data indicates a read-only operation with no capability to modify, delete, or control systems. The blast radius of misuse is minimal—an agent could only access visibility into tracked vessel data, which has no destructive or operational consequences.

From the tool's definition Tool name is 'marine_get_vessels' and description states 'Get list of tracked vessels' — a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access marine_get_vessels gives an agent:

How to control marine_get_vessels

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_get_vessels:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "marine_get_vessels": {}
  }
}

marine_get_vessels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register AetherLink SDR MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about marine_get_vessels

What does the marine_get_vessels tool do? +

Get list of tracked vessels. It is categorised as a Read tool in the AetherLink SDR MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on marine_get_vessels? +

Register the AetherLink SDR MCP server in PolicyLayer and add a rule for marine_get_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.

What risk level is marine_get_vessels? +

marine_get_vessels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit marine_get_vessels? +

Yes. Add a rate_limit block to the marine_get_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.

How do I block marine_get_vessels completely? +

Set action: deny in the PolicyLayer policy for marine_get_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.

What MCP server provides marine_get_vessels? +

marine_get_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.

Enforce policy on every AetherLink SDR MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.