hundesteuer_ranking
Ranking of German cities by Hundesteuer (first dog, per year): most expensive or cheapest, plus the national average across the covered cities.
This record as markdown: /tools/dev-crelvo-german-tax-data/hundesteuer-ranking.md
What hundesteuer_ranking does on German Tax Data
AI agents call hundesteuer_ranking 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 |
|---|---|---|---|
limit | integer | — | How many cities to return |
order | string | — |
Parameters from the server's own tool schema.
Why hundesteuer_ranking is rated Low
This tool queries and returns pre-computed or aggregated tax statistics about dog tax (Hundesteuer) rates across German cities. It retrieves information without side effects, making it a pure Read operation. The low severity reflects that misuse would only expose publicly-available municipal tax information, with minimal blast radius.
From the tool's definition Tool name and description indicate retrieval of ranking data: 'Ranking of German cities by Hundesteuer' with aggregation of 'national average.' No modification, deletion, execution, or financial action is performed.
Attacks that exploit this kind of access
The rule that runs hundesteuer_ranking 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_ranking, this is the rule to start with:
hundesteuer_ranking 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_ranking call is checked against it from then on.
Questions about hundesteuer_ranking
Ranking of German cities by Hundesteuer (first dog, per year): most expensive or cheapest, plus the national average across the covered cities. It is categorised as a Read tool in the German Tax Data MCP Server, which means it retrieves data without modifying state.
hundesteuer_ranking accepts 2 parameters: limit, order. 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_ranking: 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_ranking 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_ranking 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_ranking. 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_ranking 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