Search the live datashades.info registry of ~950 CKAN portals worldwide. Use this tool to discover which CKAN portals exist for a country, language, or topic before querying them with other CKAN tools. IMPORTANT — country parameter: always pass country name in English. If the user writes in anoth...
Risk signalsAccepts freeform code/query input (query)
Part of the Ckan server.
Free to start. No card required.
AI agents call ckan_find_portals to retrieve information from Ckan without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though ckan_find_portals only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"ckan_find_portals": {}
}
}See the full Ckan policy for all 20 tools.
These attack patterns abuse exactly the kind of access ckan_find_portals gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search the live datashades.info registry of ~950 CKAN portals worldwide. Use this tool to discover which CKAN portals exist for a country, language, or topic before querying them with other CKAN tools. IMPORTANT — country parameter: always pass country name in English. If the user writes in another language (e.g. "Italia", "España", "Brasil"), translate to English ("Italy", "Spain", "Brazil") before calling this tool. Args: - country (string): Country name in English (e.g. "Italy", "Brazil", "France") - query (string): Keyword to match against portal title (e.g. "transport", "health") - min_datasets (number): Minimum number of datasets (e.g. 100) - language (string): Portal default locale code (e.g. "it", "en", "pt_BR", "fr") - has_datastore (boolean): If true, return only portals with DataStore enabled (supports SQL queries) - limit (number): Max results to return (default 10, max 50) Returns: Ranked list of matching portals with URL, country, CKAN version, dataset count, and DataStore status. Typical workflow: ckan_find_portals (discover portal URL) → ckan_status_show (verify) → ckan_package_search (search datasets). It is categorised as a Read tool in the Ckan MCP Server, which means it retrieves data without modifying state.
Register the Ckan MCP server in PolicyLayer and add a rule for ckan_find_portals: 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 Ckan. Nothing to install.
ckan_find_portals 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 ckan_find_portals 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 ckan_find_portals. 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.
ckan_find_portals is provided by the Ckan MCP server (@aborruso/ckan-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Ckan tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.