gfw.ocean.fishing_effort
Analyze fishing effort intensity across a geographic polygon for a specified date range, aggregated by gear type (trawlers, longliners, purse seiners, squid jiggers, etc.). Returns a grid of 0.1-degree cells with fishing hours and vessel counts per month or year, drawn from Global Fishing Watch's...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gfw.ocean.fishing-effort.md
What gfw.ocean.fishing_effort does on Apibase
AI agents call gfw.ocean.fishing_effort 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 |
|---|---|---|---|
end_date | string | Yes | End of the analysis period in ISO format YYYY-MM-DD (e.g. "2023-06-30"). Must be after start_date; keep ranges under 12 months for manageable response sizes. |
start_date | string | Yes | Start of the analysis period in ISO format YYYY-MM-DD (e.g. "2023-01-01"). GFW data coverage starts from 2012. |
coordinates | array | — | Polygon boundary as an array of [longitude, latitude] pairs defining the analysis area. The polygon must be closed (first and last coordinate identical). Exampl |
temporal_resolution | string | — | Time granularity for effort aggregation. "MONTHLY" groups data by calendar month; "YEARLY" by year. Default: "MONTHLY". |
Parameters from the server's own tool schema.
Why gfw.ocean.fishing_effort is rated Low
Tool retrieves and aggregates public fishing data with no side effects or modifications.
From the tool's definition Analyze fishing effort intensity, returns grid data, AIS-based dataset, 2012–present.
Attacks that exploit this kind of access
The rule that runs gfw.ocean.fishing_effort 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.ocean.fishing_effort, this is the rule to start with:
gfw.ocean.fishing_effort 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.ocean.fishing_effort call is checked against it from then on.
Questions about gfw.ocean.fishing_effort
Analyze fishing effort intensity across a geographic polygon for a specified date range, aggregated by gear type (trawlers, longliners, purse seiners, squid jiggers, etc.). Returns a grid of 0.1-degree cells with fishing hours and vessel counts per month or year, drawn from Global Fishing Watch's public AIS-based fishing effort dataset covering 2012–present. Useful for marine protected area monitoring, fisheries research, and vessel traffic analysis. Define the study area with a closed polygon in [longitude, latitude] coordinates. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gfw.ocean.fishing_effort accepts 4 parameters: end_date, start_date, coordinates, temporal_resolution. Required: end_date, start_date. 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.ocean.fishing_effort: 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.ocean.fishing_effort 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.ocean.fishing_effort 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.ocean.fishing_effort. 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.ocean.fishing_effort 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