hundesteuer_lookup
Look up the German dog tax (Hundesteuer) for a city: annual rate for one or more dogs, listed-dog (Listenhund) surcharge, the city's pricing model, its rank among the largest cities, plus the official source and Stand. Rates verified against each municipal Satzung.
This record as markdown: /tools/dev-crelvo-german-tax-data/hundesteuer-lookup.md
What hundesteuer_lookup does on German Tax Data
AI agents call hundesteuer_lookup 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 |
|---|---|---|---|
city | string | Yes | City name or slug, e.g. "Köln", "muenchen", "Frankfurt" |
dogs | integer | — | Number of dogs (default 1) |
listed | boolean | — | Treat as a listed/dangerous-breed dog (Listenhund) if the city has a higher rate |
Parameters from the server's own tool schema.
Why hundesteuer_lookup is rated Low
This tool queries and retrieves publicly available German municipal tax rate data. It has no side effects—it merely looks up and returns tax information from an authoritative source (verified against municipal regulations). This is a pure read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Look up' and lists only retrieval actions: 'annual rate', 'surcharge', 'city's pricing model', 'rank', 'official source'. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs hundesteuer_lookup 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_lookup, this is the rule to start with:
hundesteuer_lookup 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_lookup call is checked against it from then on.
Questions about hundesteuer_lookup
Look up the German dog tax (Hundesteuer) for a city: annual rate for one or more dogs, listed-dog (Listenhund) surcharge, the city's pricing model, its rank among the largest cities, plus the official source and Stand. Rates verified against each municipal Satzung. It is categorised as a Read tool in the German Tax Data MCP Server, which means it retrieves data without modifying state.
hundesteuer_lookup accepts 3 parameters: city, dogs, listed. Required: city. 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 hundesteuer_lookup: 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_lookup 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_lookup 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_lookup. 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_lookup 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