Low Risk

ch_get_departures

Get departure board for a Swiss train station with real-time information.

Part of the Public Transport server.

ch_get_departures is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PUBLIC TRANSPORT →

Free to start. No card required.

AI agents call ch_get_departures to retrieve information from Public Transport without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ch_get_departures only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ch_get_departures": {}
  }
}

See the full Public Transport policy for all 12 tools.

Get this rule live on your own Public Transport server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PUBLIC TRANSPORT →

View all 12 tools →

These attack patterns abuse exactly the kind of access ch_get_departures gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ch_get_departures only ever does what you allow.

SECURE PUBLIC TRANSPORT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ch_get_departures tool do? +

Get departure board for a Swiss train station with real-time information.. It is categorised as a Read tool in the Public Transport MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ch_get_departures? +

Register the Public Transport MCP server in PolicyLayer and add a rule for ch_get_departures: 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 Public Transport. Nothing to install.

What risk level is ch_get_departures? +

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

Can I rate-limit ch_get_departures? +

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

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

ch_get_departures is provided by the Public Transport MCP server (mirodn/mcp-server-public-transport). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Public Transport tool call.

Deterministic rules across all 12 Public Transport tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.