search_stadtratsbeschluesse
AI agents call search_stadtratsbeschluesse to retrieve information from Zurich Open Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries public data (City Council decisions) without side effects. It performs a search operation, which is a Read category action. The Zurich Open Data server provides public datasets, and parliamentary proceedings are typically public information. Severity is low because the data is public and no modifications are possible.
From the tool's definition Tool name 'search_stadtratsbeschluesse' indicates searching City Council decisions (Stadtratsbeschlüsse). Sibling tools like 'get_beschluesse_by_departement' and 'get_stadtratsbeschluss_detail' are clearly retrieval operations.
Documented attack patterns abuse exactly the kind of access search_stadtratsbeschluesse 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 search_stadtratsbeschluesse:
{
"version": "1",
"default": "deny",
"tools": {
"search_stadtratsbeschluesse": {}
}
} search_stadtratsbeschluesse is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_stadtratsbeschluesse. It is categorised as a Read tool in the Zurich Open Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zurich Open Data MCP Server MCP server in PolicyLayer and add a rule for search_stadtratsbeschluesse: 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.
search_stadtratsbeschluesse 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 search_stadtratsbeschluesse 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 search_stadtratsbeschluesse. 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.
search_stadtratsbeschluesse 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.