copernicus-sentinel.imagery.search
Search the Copernicus Data Space Ecosystem STAC catalog for Sentinel satellite scenes covering an area and date range, with optional maximum cloud cover filter and sort by date or cloudiness. Returns scene IDs, acquisition time, cloud cover, and a quicklook thumbnail URL for each match. Data: ESA...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/copernicus-sentinel.imagery.search.md
What copernicus-sentinel.imagery.search does on Apibase
AI agents call copernicus-sentinel.imagery.search 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 |
|---|---|---|---|
lat | number | — | Latitude of a point of interest. Use with "lon" (and optional "radius_km") instead of bbox. |
lon | number | — | Longitude of a point of interest. Use with "lat" (and optional "radius_km") instead of bbox. |
bbox | array | — | Bounding box [min_lon, min_lat, max_lon, max_lat] in WGS84 decimal degrees. Provide this OR lat + lon. |
sort | string | — | Sort order: "date_desc" (newest first, default) or "cloud_asc" (least cloudy first). |
limit | integer | — | Maximum number of scenes to return (default 10, max 50). |
end_date | string | Yes | End of the acquisition date range, format YYYY-MM-DD. |
radius_km | number | — | Search radius in kilometers around lat/lon (default 20, max 500). Ignored if bbox is given. |
collection | string | — | STAC collection ID to search (default "sentinel-2-l2a"). Other common values: "sentinel-1-grd" (radar), "sentinel-2-l1c" (top-of-atmosphere optical), "sentinel- |
start_date | string | Yes | Start of the acquisition date range, format YYYY-MM-DD. |
max_cloud_cover | number | — | Maximum acceptable cloud cover percentage (0-100). Applies to optical collections like Sentinel-2; omit for radar collections such as Sentinel-1. |
Parameters from the server's own tool schema.
Why copernicus-sentinel.imagery.search is rated Low
Queries public satellite imagery metadata catalog; retrieves information only, no side effects.
From the tool's definition Search STAC catalog, returns scene IDs and metadata, no auth required
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs copernicus-sentinel.imagery.search 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 copernicus-sentinel.imagery.search, this is the rule to start with:
copernicus-sentinel.imagery.search 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 copernicus-sentinel.imagery.search call is checked against it from then on.
Questions about copernicus-sentinel.imagery.search
Search the Copernicus Data Space Ecosystem STAC catalog for Sentinel satellite scenes covering an area and date range, with optional maximum cloud cover filter and sort by date or cloudiness. Returns scene IDs, acquisition time, cloud cover, and a quicklook thumbnail URL for each match. Data: ESA/EU Copernicus Sentinel program, public STAC catalog, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
copernicus-sentinel.imagery.search accepts 10 parameters: lat, lon, bbox, sort, limit, end_date, radius_km, collection, start_date, max_cloud_cover. 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 copernicus-sentinel.imagery.search: 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.
copernicus-sentinel.imagery.search 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 copernicus-sentinel.imagery.search 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 copernicus-sentinel.imagery.search. 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.
copernicus-sentinel.imagery.search 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