list_datasets

SERVERGerman Tax Data SOURCEhttps://data.crelvo.dev/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-crelvo-german-tax-data/list-datasets.md

WHAT IT DOES

What list_datasets does on German Tax Data

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

RISK

Why list_datasets is rated Low

This tool retrieves and enumerates metadata about available datasets without modifying, executing, or deleting anything. It is purely informational, making it a Read category tool with low severity since the data returned is about dataset availability and source information rather than sensitive personal tax data itself.

From the tool's definition Tool name is 'list_datasets' and description states 'List the available...datasets', which is a retrieval operation with no side effects. It explicitly states 'Call this first to see what you can query', indicating it is an informational/discovery tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_datasets 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 list_datasets, this is the rule to start with:

list_datasets Allowed

list_datasets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_datasets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect German Tax Data, apply this rule, and every list_datasets call is checked against it from then on.

FAQ

Questions about list_datasets

What does the list_datasets tool do? +

List the available hand-verified German municipal tax/fee datasets (Hundesteuer, Zweitwohnungsteuer, Pfändung), their coverage, source sites and refresh cadence. Call this first to see what you can query. It is categorised as a Read tool in the German Tax Data MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_datasets? +

Register the German Tax Data MCP server in PolicyLayer and add a rule for list_datasets: 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.

What risk level is list_datasets? +

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

Can I rate-limit list_datasets? +

Yes. Add a rate_limit block to the list_datasets 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 list_datasets completely? +

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

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

KEEP EXPLORING

More on German Tax Data, and thousands of servers like it.

This server

All 9 German Tax Data tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →