Get complete metadata for a specific dataset (package). Returns full details including resources, organization, tags, and all metadata fields. Notes: - metadata_modified is a CKAN record timestamp (publish time on source portals, harvest time on aggregators), not the content date. - iss...
Single-target operation
Part of the Ckan MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call ckan_package_show 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_package_show 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.
tools:
ckan_package_show:
rules:
- action: allowSee the full Ckan policy for all 20 tools.
Agents calling read-class tools like ckan_package_show have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get complete metadata for a specific dataset (package). Returns full details including resources, organization, tags, and all metadata fields. Notes: - metadata_modified is a CKAN record timestamp (publish time on source portals, harvest time on aggregators), not the content date. - issued/modified are content dates when provided by the publisher. - JSON output adds metadata_harvested_at (same as metadata_modified). Args: - server_url (string): Base URL of CKAN server - id (string): Dataset ID or name (machine-readable slug) - include_tracking (boolean): Include view/download statistics (default: false) - response_format ('markdown' | 'json'): Output format Returns (JSON format): id, name, title, notes, organization, tags, state, license_title, metadata_created, metadata_modified, issued, modified, author, maintainer, frequency, language, publisher_name, holder_name, hvd_category, applicable_legislation, resources (id, name, format, url, size, datastore_active, created, last_modified, api_json_url), view_url, api_json_url Examples: - { server_url: "https://dati.gov.it/opendata", id: "dataset-name" } - { server_url: "...", id: "abc-123-def", include_tracking: true } Typical workflow: ckan_package_show → pick a resource with datastore_active=true → ckan_datastore_search (query its data). It is categorised as a Read tool in the Ckan MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for ckan_package_show. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ckan MCP server.
ckan_package_show 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_package_show rule in your Intercept 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 Intercept policy for ckan_package_show. 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_package_show is provided by the Ckan MCP server (@aborruso/ckan-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept