data-europa.reference.catalogue_list
List the ~211 national, regional, and EU-institution data catalogues (portal source ids, e.g. "gdi-de", "govdata", "geocat-li") that feed the EU Open Data Portal, optionally filtered by an id substring. Data: data.europa.eu Hub-Search API, no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/data-europa.reference.catalogue-list.md
What data-europa.reference.catalogue_list does on Apibase
AI agents call data-europa.reference.catalogue_list 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 | — | Max catalogues to return (1-211, default 50) |
query | string | — | Substring filter on catalogue id (e.g. "geo" matches "geocat-li", "gdi-de") |
Parameters from the server's own tool schema.
Why data-europa.reference.catalogue_list is rated Low
Retrieves publicly available catalogue metadata from EU Open Data Portal without side effects.
From the tool's definition List the ~211 national, regional, and EU-institution data catalogues, no auth required.
Attacks that exploit this kind of access
The rule that runs data-europa.reference.catalogue_list 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 data-europa.reference.catalogue_list, this is the rule to start with:
data-europa.reference.catalogue_list 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 data-europa.reference.catalogue_list call is checked against it from then on.
Questions about data-europa.reference.catalogue_list
List the ~211 national, regional, and EU-institution data catalogues (portal source ids, e.g. "gdi-de", "govdata", "geocat-li") that feed the EU Open Data Portal, optionally filtered by an id substring. Data: data.europa.eu Hub-Search API, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
data-europa.reference.catalogue_list accepts 2 parameters: limit, query. 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 data-europa.reference.catalogue_list: 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.
data-europa.reference.catalogue_list 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 data-europa.reference.catalogue_list 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 data-europa.reference.catalogue_list. 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.
data-europa.reference.catalogue_list 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