db-list-stations

Search for stations in the Deutsche Bahn rail network (live data).

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/db-list-stations.md

WHAT IT DOES

What db-list-stations does on Meta Data Mcp

AI agents call db-list-stations to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why db-list-stations is rated Low

This tool searches and retrieves publicly available Deutsche Bahn station data. It performs a read-only query against live data with no side effects, data modification, code execution, or financial impact. The blast radius of misuse is minimal—an agent could only retrieve station information already publicly available.

From the tool's definition Tool name 'db-list-stations' and description 'Search for stations in the Deutsche Bahn rail network (live data)' indicates a query operation that retrieves station information without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs db-list-stations safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For db-list-stations, this is the rule to start with:

db-list-stations Allowed

db-list-stations 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": {
    "db-list-stations": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every db-list-stations call is checked against it from then on.

FAQ

Questions about db-list-stations

What does the db-list-stations tool do? +

Search for stations in the Deutsche Bahn rail network (live data). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on db-list-stations? +

Register the Meta Data MCP server in PolicyLayer and add a rule for db-list-stations: 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 Meta Data Mcp. Nothing to install.

What risk level is db-list-stations? +

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

Can I rate-limit db-list-stations? +

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

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

db-list-stations is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta 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 →