zweitwohnungsteuer_changes
List German cities that changed (raised or newly introduced) their Zweitwohnungsteuer in a given year — the fresh-news angle. Defaults to 2026 (Stuttgart, Chemnitz, Heidelberg doubled to 20%, etc.).
This record as markdown: /tools/dev-crelvo-german-tax-data/zweitwohnungsteuer-changes.md
What zweitwohnungsteuer_changes does on German Tax Data
AI agents call zweitwohnungsteuer_changes to retrieve information from German Tax Data without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | integer | — |
Parameters from the server's own tool schema.
Why zweitwohnungsteuer_changes is rated Low
This tool queries and retrieves historical tax policy change data from a database. It performs a read-only lookup operation to surface information about municipal tax rate changes. There is no modification, deletion, execution of code, or financial operation involved. The tool simply surfaces publicly available tax policy information cited to source.
From the tool's definition Tool name 'zweitwohnungsteuer_changes' and description 'List German cities that changed... their Zweitwohnungsteuer in a given year' — the verb 'List' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs zweitwohnungsteuer_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and German Tax Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zweitwohnungsteuer_changes, this is the rule to start with:
zweitwohnungsteuer_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect German Tax Data, apply this rule, and every zweitwohnungsteuer_changes call is checked against it from then on.
Questions about zweitwohnungsteuer_changes
List German cities that changed (raised or newly introduced) their Zweitwohnungsteuer in a given year — the fresh-news angle. Defaults to 2026 (Stuttgart, Chemnitz, Heidelberg doubled to 20%, etc.). It is categorised as a Read tool in the German Tax Data MCP Server, which means it retrieves data without modifying state.
zweitwohnungsteuer_changes accepts 1 parameter: year. The full parameter table on this page comes from the server's own tool schema.
Register the German Tax Data MCP server in PolicyLayer and add a rule for zweitwohnungsteuer_changes: 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 German Tax Data. Nothing to install.
zweitwohnungsteuer_changes 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 zweitwohnungsteuer_changes 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 zweitwohnungsteuer_changes. 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.
zweitwohnungsteuer_changes is provided by the German Tax Data MCP server (https://data.crelvo.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on German Tax Data, and thousands of servers like it.
This server
Across the catalogue