High Risk →

no_stop_departures

Upcoming departures for a StopPlace ID (e.g., 'NSR:StopPlace:58368').

Part of the Public Transport MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke no_stop_departures to trigger processes or run actions in Public Transport. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

no_stop_departures can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

mirodn-mcp-server-public-transport.yaml
tools:
  no_stop_departures:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Public Transport policy for all 12 tools.

Tool Name no_stop_departures
Category Execute
Risk Level High

View all 12 tools →

Agents calling execute-class tools like no_stop_departures have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

no_stop_departures is one of the high-risk operations in Public Transport. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the no_stop_departures tool do? +

Upcoming departures for a StopPlace ID (e.g., 'NSR:StopPlace:58368').. It is categorised as a Execute tool in the Public Transport MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on no_stop_departures? +

Add a rule in your Intercept YAML policy under the tools section for no_stop_departures. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Public Transport MCP server.

What risk level is no_stop_departures? +

no_stop_departures is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit no_stop_departures? +

Yes. Add a rate_limit block to the no_stop_departures rule in your Intercept 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 no_stop_departures completely? +

Set action: deny in the Intercept policy for no_stop_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 no_stop_departures? +

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

Enforce policies on Public Transport

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.