Run SQL queries on a CKAN DataStore resource. This endpoint is only available on CKAN portals with DataStore enabled and SQL access exposed. Args: - server_url (string): Base URL of CKAN server - sql (string): SQL query (e.g., SELECT * FROM "resource_id" LIMIT 10) - response_format ('markdown' | ...
Risk signalsAccepts freeform code/query input (sql)
Part of the Ckan server.
Free to start. No card required.
AI agents call ckan_datastore_search_sql 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_datastore_search_sql 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_datastore_search_sql": {}
}
}See the full Ckan policy for all 20 tools.
These attack patterns abuse exactly the kind of access ckan_datastore_search_sql 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.
Run SQL queries on a CKAN DataStore resource. This endpoint is only available on CKAN portals with DataStore enabled and SQL access exposed. Args: - server_url (string): Base URL of CKAN server - sql (string): SQL query (e.g., SELECT * FROM "resource_id" LIMIT 10) - response_format ('markdown' | 'json'): Output format Returns: SQL query results from DataStore Examples: - { server_url: "...", sql: "SELECT * FROM "abc-123" LIMIT 10" } - { server_url: "...", sql: "SELECT COUNT(*) AS total FROM "abc-123"" } Typical workflow: ckan_package_show (get resource_id) → ckan_datastore_search_sql (run SQL on it) Security note: SQL queries are forwarded directly to the CKAN DataStore API. The CKAN server enforces its own access controls and read-only permissions. No local database is exposed. Queries are limited to public DataStore resources on the target portal.. 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_datastore_search_sql: 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_datastore_search_sql 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_datastore_search_sql 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_datastore_search_sql. 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_datastore_search_sql 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.