Low Risk

get_beschluesse_by_departement

get_beschluesse_by_departement

How to control get_beschluesse_by_departement ↓

What get_beschluesse_by_departement does on Zurich Open Data MCP Server

AI agents call get_beschluesse_by_departement 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.

Low Risk

Why get_beschluesse_by_departement needs a policy

This tool retrieves public legislative/administrative records from Zurich's open data, filtered by department. No description is provided, but the naming pattern and context from sibling tools (all read operations on public datasets) indicate this is a query/retrieval operation with no side effects. The data being accessed is publicly available parliamentary proceedings.

From the tool's definition Tool name 'get_beschluesse_by_departement' suggests retrieval of parliamentary/administrative decisions ('Beschlüsse') filtered by department.

Documented attack patterns abuse exactly the kind of access get_beschluesse_by_departement gives an agent:

How to control get_beschluesse_by_departement

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 get_beschluesse_by_departement:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_beschluesse_by_departement": {}
  }
}

get_beschluesse_by_departement is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zurich Open Data MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_beschluesse_by_departement

What does the get_beschluesse_by_departement tool do? +

get_beschluesse_by_departement. It is categorised as a Read tool in the Zurich Open Data MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_beschluesse_by_departement? +

Register the Zurich Open Data MCP Server MCP server in PolicyLayer and add a rule for get_beschluesse_by_departement: 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.

What risk level is get_beschluesse_by_departement? +

get_beschluesse_by_departement is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_beschluesse_by_departement? +

Yes. Add a rate_limit block to the get_beschluesse_by_departement 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.

How do I block get_beschluesse_by_departement completely? +

Set action: deny in the PolicyLayer policy for get_beschluesse_by_departement. 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.

What MCP server provides get_beschluesse_by_departement? +

get_beschluesse_by_departement 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.

Enforce policy on every Zurich Open Data MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.