copernicus-sentinel.imagery.collections
Browse the Copernicus Data Space Ecosystem STAC catalog of satellite/product collections (Sentinel-1 radar, Sentinel-2 optical, Sentinel-3 ocean/land, Sentinel-5P atmosphere, Sentinel-6 altimetry, plus Copernicus contributing missions and derived land/emergency products), filterable by keyword. U...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/copernicus-sentinel.imagery.collections.md
What copernicus-sentinel.imagery.collections does on Apibase
AI agents call copernicus-sentinel.imagery.collections 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 | — | Maximum number of collections to return (default 20, max 100). |
keyword | string | — | Filter collections by keyword matched against collection ID and title (case-insensitive substring), e.g. "sentinel-1" or "dem". Omit to list only the Sentinel m |
Parameters from the server's own tool schema.
Why copernicus-sentinel.imagery.collections is rated Low
Tool queries publicly available satellite imagery metadata collections without side effects or data retrieval.
From the tool's definition Browse STAC catalog, filterable by keyword, no auth required
Attacks that exploit this kind of access
The rule that runs copernicus-sentinel.imagery.collections 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.collections, this is the rule to start with:
copernicus-sentinel.imagery.collections 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.collections call is checked against it from then on.
Questions about copernicus-sentinel.imagery.collections
Browse the Copernicus Data Space Ecosystem STAC catalog of satellite/product collections (Sentinel-1 radar, Sentinel-2 optical, Sentinel-3 ocean/land, Sentinel-5P atmosphere, Sentinel-6 altimetry, plus Copernicus contributing missions and derived land/emergency products), filterable by keyword. Use the returned collection IDs with search_scenes and scene_detail. Data: ESA/EU Copernicus, 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.collections accepts 2 parameters: limit, keyword. 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.collections: 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.collections 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.collections 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.collections. 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.collections 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