Führt eine SQL-Abfrage auf dem CKAN DataStore aus.
AI agents invoke zurich_datastore_sql to trigger actions in Zurich Open Data MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary SQL queries against a datastore. While it appears to target a public open data platform (read-only by intent), SQL execution tools can potentially be misused to run destructive queries (DROP, DELETE) or expensive queries that cause denial-of-service.
From the tool's definition 'Führt eine SQL-Abfrage auf dem CKAN DataStore aus' — executes an SQL query on the CKAN DataStore
Documented attack patterns abuse exactly the kind of access zurich_datastore_sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zurich Open Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for zurich_datastore_sql:
{
"version": "1",
"default": "deny",
"tools": {
"zurich_datastore_sql": {
"limits": [
{
"counter": "zurich_datastore_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}zurich_datastore_sql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Führt eine SQL-Abfrage auf dem CKAN DataStore aus. It is categorised as a Execute tool in the Zurich Open Data MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zurich Open Data MCP Server MCP server in PolicyLayer and add a rule for zurich_datastore_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 Zurich Open Data MCP Server. Nothing to install.
zurich_datastore_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zurich_datastore_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 zurich_datastore_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.
zurich_datastore_sql is provided by the Zurich Open Data MCP Server MCP server (pypi:zurich-opendata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zurich Open Data MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Zurich Open Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.