Search datasets and inspect the DataStore schema of queryable resources. For each dataset found, lists all resources. For DataStore-enabled resources, fetches the full field schema (name, type, and label/notes when available) plus total record count — all in one call. Use this before ckan_datasto...
Part of the Ckan server.
Free to start. No card required.
AI agents call ckan_analyze_datasets 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_analyze_datasets 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_analyze_datasets": {}
}
}See the full Ckan policy for all 20 tools.
These attack patterns abuse exactly the kind of access ckan_analyze_datasets 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 datasets and inspect the DataStore schema of queryable resources. For each dataset found, lists all resources. For DataStore-enabled resources, fetches the full field schema (name, type, and label/notes when available) plus total record count — all in one call. Use this before ckan_datastore_search to understand what fields are available and what data to expect. Args: - server_url (string): Base URL of CKAN server - q (string): Solr search query (e.g. "incidenti", "title:ambiente") - rows (number): Max datasets to analyze (default 5, max 20) - response_format ('markdown' | 'json'): Output format Returns: For each dataset: title, ID, organization, and per DataStore resource: field schema with label/notes (when available from DataStore Dictionary) and record count. Typical workflow: ckan_analyze_datasets → ckan_datastore_search (with known field names). 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_analyze_datasets: 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_analyze_datasets 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_analyze_datasets 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_analyze_datasets. 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_analyze_datasets 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.