Gibt einen Ueberblick ueber den gesamten Open-Data-Katalog des Landes Berlin.
AI agents call berlin_catalog_stats to retrieve information from Berlin Open Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes catalog metadata—a purely informational read operation. No data is created, modified, executed, or destroyed. The blast radius of misuse is minimal (e.g., excessive requests could cause DoS, but the tool itself is not destructive or dangerous). Categorized as Read with low severity.
From the tool's definition Tool name 'berlin_catalog_stats' and description indicate it 'provides an overview of the entire Open Data catalog of the state of Berlin' (translated from German).
Documented attack patterns abuse exactly the kind of access berlin_catalog_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Berlin Open Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for berlin_catalog_stats:
{
"version": "1",
"default": "deny",
"tools": {
"berlin_catalog_stats": {}
}
}berlin_catalog_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gibt einen Ueberblick ueber den gesamten Open-Data-Katalog des Landes Berlin. It is categorised as a Read tool in the Berlin Open Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Berlin Open Data MCP Server MCP server in PolicyLayer and add a rule for berlin_catalog_stats: 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 Berlin Open Data MCP Server. Nothing to install.
berlin_catalog_stats 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 berlin_catalog_stats 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 berlin_catalog_stats. 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.
berlin_catalog_stats is provided by the Berlin Open Data MCP Server MCP server (tifa365/berlin-opendata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Berlin Open Data MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Berlin Open Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.