tripgo-departures
AI agents call tripgo-departures to retrieve information from TripGo 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 real-time or scheduled public transport departure data with no side effects on user data or systems. It is a pure read operation that queries transport information from the TripGo API. The low severity reflects minimal risk—misuse would only surface existing public transit data, not modify systems, execute code, or cause financial harm.
From the tool's definition Tool name 'tripgo-departures' and context indicate this retrieves public transport departure information. Server description states it provides 'public transport departures' and 'retrieve travel information.' No description text provided for the tool itself,…
Attacks that exploit this kind of access
tripgo-departures. It is categorised as a Read tool in the TripGo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TripGo MCP Server MCP server in PolicyLayer and add a rule for tripgo-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 TripGo MCP Server. Nothing to install.
tripgo-departures 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 tripgo-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.
Set action: deny in the PolicyLayer policy for tripgo-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.
tripgo-departures is provided by the TripGo MCP Server MCP server (skedgo/tripgo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →