gfw.vessel.details
Retrieve complete identity and activity profile for a specific vessel using its Global Fishing Watch vessel UUID. Returns self-reported AIS data (name, flag, MMSI, IMO, call sign), inferred gear and ship types from neural-network analysis of movement patterns, official registry records (where ava...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gfw.vessel.details.md
What gfw.vessel.details does on Apibase
AI agents call gfw.vessel.details to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
vessel_id | string | Yes | Global Fishing Watch vessel UUID as returned by gfw.vessel.search (e.g. "1f1f12b24-4dfb-e5c8-90b0-32f8e79402c1"). |
Parameters from the server's own tool schema.
Why gfw.vessel.details is rated Low
Queries vessel data via UUID; no modification, deletion, or external action triggered.
From the tool's definition Retrieve complete identity and activity profile for a specific vessel
Attacks that exploit this kind of access
The rule that runs gfw.vessel.details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gfw.vessel.details, this is the rule to start with:
gfw.vessel.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every gfw.vessel.details call is checked against it from then on.
Questions about gfw.vessel.details
Retrieve complete identity and activity profile for a specific vessel using its Global Fishing Watch vessel UUID. Returns self-reported AIS data (name, flag, MMSI, IMO, call sign), inferred gear and ship types from neural-network analysis of movement patterns, official registry records (where available), and AIS coverage statistics (total messages, positions, active date range). Vessel UUIDs are obtained from gfw.vessel.search. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gfw.vessel.details accepts 1 parameter: vessel_id. Required: vessel_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for gfw.vessel.details: 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 Apibase. Nothing to install.
gfw.vessel.details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gfw.vessel.details 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 gfw.vessel.details. 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.
gfw.vessel.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue