hundesteuer_by_state
Average German dog tax (Hundesteuer, first dog per year) per Bundesland (federal state), aggregated over the covered largest cities — the data behind the Deutschlandkarte. Answers 'which German state has the highest/lowest dog tax'. Note: a mean over cities, not an official state rate (the tax is...
This record as markdown: /tools/dev-crelvo-german-tax-data/hundesteuer-by-state.md
What hundesteuer_by_state does on German Tax Data
AI agents call hundesteuer_by_state 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.
Why hundesteuer_by_state is rated Low
This tool performs a data retrieval and aggregation function with no side effects. It returns statistical summaries of municipal tax rates across federal states—purely informational queries. No data is created, modified, deleted, or executed; no financial transactions occur. The aggregation is read-only analysis of publicly cited tax data.
From the tool's definition Tool retrieves and aggregates pre-calculated average dog tax data by German federal state. Description explicitly states it answers 'which German state has the highest/lowest dog tax', indicating a query/lookup operation returning existing aggregated…
Attacks that exploit this kind of access
The rule that runs hundesteuer_by_state 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 hundesteuer_by_state, this is the rule to start with:
hundesteuer_by_state 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 hundesteuer_by_state call is checked against it from then on.
Questions about hundesteuer_by_state
Average German dog tax (Hundesteuer, first dog per year) per Bundesland (federal state), aggregated over the covered largest cities — the data behind the Deutschlandkarte. Answers 'which German state has the highest/lowest dog tax'. Note: a mean over cities, not an official state rate (the tax is municipal). It is categorised as a Read tool in the German Tax Data MCP Server, which means it retrieves data without modifying state.
Register the German Tax Data MCP server in PolicyLayer and add a rule for hundesteuer_by_state: 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.
hundesteuer_by_state 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 hundesteuer_by_state 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 hundesteuer_by_state. 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.
hundesteuer_by_state 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