gfw.vessel.fishing_events
Retrieve AIS-detected maritime events for a specific vessel — either fishing activity episodes or port visits. Fishing events capture when a vessel slowed and maneuvered in patterns consistent with active fishing (coordinates, duration, EEZ/RFMO/FAO area codes, distance from shore and port). Port...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gfw.vessel.fishing-events.md
What gfw.vessel.fishing_events does on Apibase
AI agents call gfw.vessel.fishing_events 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 |
|---|---|---|---|
limit | integer | — | Number of events per page (1–50, default 10). |
offset | integer | — | Pagination offset — number of events to skip (default 0). |
end_date | string | — | Filter events ending on or before this date in ISO format YYYY-MM-DD (e.g. "2023-12-31"). |
vessel_id | string | Yes | GFW vessel UUID as returned by gfw.vessel.search (e.g. "1f1f12b24-4dfb-e5c8-90b0-32f8e79402c1"). |
event_type | string | — | Type of maritime event to retrieve. "fishing" returns AIS-detected fishing activity events; "port_visit" returns port calls and anchorage stops. Default: "fishi |
start_date | string | — | Filter events starting on or after this date in ISO format YYYY-MM-DD (e.g. "2023-01-01"). |
Parameters from the server's own tool schema.
Why gfw.vessel.fishing_events is rated Low
Tool retrieves historical vessel tracking data with no side effects or state modifications.
From the tool's definition Retrieve AIS-detected maritime events; captures fishing activity, port visits; paginated results.
Attacks that exploit this kind of access
The rule that runs gfw.vessel.fishing_events 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.fishing_events, this is the rule to start with:
gfw.vessel.fishing_events 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.fishing_events call is checked against it from then on.
Questions about gfw.vessel.fishing_events
Retrieve AIS-detected maritime events for a specific vessel — either fishing activity episodes or port visits. Fishing events capture when a vessel slowed and maneuvered in patterns consistent with active fishing (coordinates, duration, EEZ/RFMO/FAO area codes, distance from shore and port). Port visits capture anchorage and berthing stops (port name, flag, entry/exit times). Results are paginated; use offset for subsequent pages. Vessel UUID is 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.fishing_events accepts 6 parameters: limit, offset, end_date, vessel_id, event_type, start_date. 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.fishing_events: 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.fishing_events 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.fishing_events 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.fishing_events. 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.fishing_events 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