Ruft vollstaendige Metadaten und Ressourcen eines Datensatzes ab.
AI agents call berlin_get_dataset 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.
The tool performs a read-only query operation that fetches dataset metadata and resources from Berlin's open data catalog. There are no side effects, no data modifications, no code execution, and no destructive operations. The blast radius of misuse is minimal—an agent could only retrieve metadata it is authorized to access, which is the intended use case for a public open data catalog.
From the tool's definition Tool retrieves complete metadata and resources of a dataset ("Ruft vollstaendige Metadaten und Ressourcen eines Datensatzes ab"). No modification, deletion, or execution of code is indicated. This is a data retrieval operation.
Documented attack patterns abuse exactly the kind of access berlin_get_dataset 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_get_dataset:
{
"version": "1",
"default": "deny",
"tools": {
"berlin_get_dataset": {}
}
}berlin_get_dataset 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.
Ruft vollstaendige Metadaten und Ressourcen eines Datensatzes ab. 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_get_dataset: 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_get_dataset 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_get_dataset 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_get_dataset. 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_get_dataset 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.